Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4e27be83a01258dc049cc4f7a357c676733c2a755be46a9f7519ae161f3d80c

Tx prefix hash: 99e507e48fc08a4a3d0bbf48f988dc7d47a17cb2627560c3a882be4dab3a28d2
Tx public key: 16972fcf3296bea01bdc46f12eaa9cf7fb1033a46626b797ce622eaee93ee1ff
Timestamp: 1728779304 Timestamp [UCT]: 2024-10-13 00:28:24 Age [y:d:h:m:s]: 00:173:20:35:00
Block: 1130350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124029 RingCT/type: yes/0
Extra: 0116972fcf3296bea01bdc46f12eaa9cf7fb1033a46626b797ce622eaee93ee1ff02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6623921a2f334ebc885f88fbae6d11b3405cc4ab9cf1f007ed65d98e5454fa1 0.600000000000 1613225 of 15

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": 1130360, "vin": [ { "gen": { "height": 1130350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6623921a2f334ebc885f88fbae6d11b3405cc4ab9cf1f007ed65d98e5454fa1" } } ], "extra": [ 1, 22, 151, 47, 207, 50, 150, 190, 160, 27, 220, 70, 241, 46, 170, 156, 247, 251, 16, 51, 164, 102, 38, 183, 151, 206, 98, 46, 174, 233, 62, 225, 255, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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