Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23aed2def0ca2f436e0ad67f13e1389f78184315430dbccd18984430d92b1e69

Tx prefix hash: 60dc6ebcc08cf8b08fc496fe266bef4877af2b19c11014fafafa751c0934f7cf
Tx public key: 455a514bb104926be2fd5ee3f0d1375034fc68a0a21c6ebf2f8c4567ff7cafec
Timestamp: 1719437355 Timestamp [UCT]: 2024-06-26 21:29:15 Age [y:d:h:m:s]: 00:304:17:36:54
Block: 1052876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217786 RingCT/type: yes/0
Extra: 01455a514bb104926be2fd5ee3f0d1375034fc68a0a21c6ebf2f8c4567ff7cafec02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a18a6fd61e82a648a8ddd98e3583d1bc171add8a896ee8f6a1c719757d7bf769 0.600000000000 1523211 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": 1052886, "vin": [ { "gen": { "height": 1052876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a18a6fd61e82a648a8ddd98e3583d1bc171add8a896ee8f6a1c719757d7bf769" } } ], "extra": [ 1, 69, 90, 81, 75, 177, 4, 146, 107, 226, 253, 94, 227, 240, 209, 55, 80, 52, 252, 104, 160, 162, 28, 110, 191, 47, 140, 69, 103, 255, 124, 175, 236, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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