Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4ef944c1a3b379191fa22c0b2d0af321a3a3005ac5f0b80fe49c9bdb1fbd7e65

Tx prefix hash: 503b43b0bcf2de28c5e1c0f6dcad9493bf79d1a5abadd7443218b8fb669140d7
Tx public key: 433da988b01072561aaa7b731413e8df834743fb7d0feabfcdff384222cfbbbd
Timestamp: 1577564358 Timestamp [UCT]: 2019-12-28 20:19:18 Age [y:d:h:m:s]: 05:067:16:36:34
Block: 33807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1198165 RingCT/type: yes/0
Extra: 01433da988b01072561aaa7b731413e8df834743fb7d0feabfcdff384222cfbbbd021100000005d81c26c0000000000000000000

1 output(s) for total of 474.224766924000 dcy

stealth address amount amount idx
00: 31fb5fa6f027dc5f355171cdf56bf7f3ad17f0f5a60f2e05fbe9cd35a6127958 474.224766924000 56733 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 33817, "vin": [ { "gen": { "height": 33807 } } ], "vout": [ { "amount": 474224766924, "target": { "key": "31fb5fa6f027dc5f355171cdf56bf7f3ad17f0f5a60f2e05fbe9cd35a6127958" } } ], "extra": [ 1, 67, 61, 169, 136, 176, 16, 114, 86, 26, 170, 123, 115, 20, 19, 232, 223, 131, 71, 67, 251, 125, 15, 234, 191, 205, 255, 56, 66, 34, 207, 187, 189, 2, 17, 0, 0, 0, 5, 216, 28, 38, 192, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8