Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11bb7902cf2f182f343f74bb3c54a38b117d4972a8b83f0a1eabe28c1f39fb74

Tx prefix hash: 568c3c0d47ce85551d410fd1fb03c4a950e1f2aa0fa36c034d3fcdbfad9b3ad7
Tx public key: 239d9518fabe693490c4b2a99436deda93f6434c3ed9354aff10a356fce00948
Timestamp: 1636173168 Timestamp [UCT]: 2021-11-06 04:32:48 Age [y:d:h:m:s]: 02:237:23:35:10
Block: 368333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 687620 RingCT/type: yes/0
Extra: 01239d9518fabe693490c4b2a99436deda93f6434c3ed9354aff10a356fce009480211000000014f792ffd000000000000000000

1 output(s) for total of 36.945390855000 dcy

stealth address amount amount idx
00: c75689284a79fe4055e64f99401916476a373d64d7eaa200fd1bb85b4b803027 36.945390855000 747121 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": 368343, "vin": [ { "gen": { "height": 368333 } } ], "vout": [ { "amount": 36945390855, "target": { "key": "c75689284a79fe4055e64f99401916476a373d64d7eaa200fd1bb85b4b803027" } } ], "extra": [ 1, 35, 157, 149, 24, 250, 190, 105, 52, 144, 196, 178, 169, 148, 54, 222, 218, 147, 246, 67, 76, 62, 217, 53, 74, 255, 16, 163, 86, 252, 224, 9, 72, 2, 17, 0, 0, 0, 1, 79, 121, 47, 253, 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