Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4a5344e353836461274b96424c441f53b3279013491a00635211dd7b721b35f

Tx prefix hash: 670e27401cae1070f6e11ba436ce2f67c8d2a8d0431ce9ea9719e6ba86a6d7a0
Tx public key: 90af037a0eea7bf410e11d2c2606b5bd3aa03d720c63588918c1058f3aeda3ee
Timestamp: 1730938220 Timestamp [UCT]: 2024-11-07 00:10:20 Age [y:d:h:m:s]: 00:219:06:26:11
Block: 1148151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156510 RingCT/type: yes/0
Extra: 0190af037a0eea7bf410e11d2c2606b5bd3aa03d720c63588918c1058f3aeda3ee0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 565cf7f9ed4efa5120060905f152234cc28b1474d952b20bd33bda5ac35d1304 0.600000000000 1632936 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": 1148161, "vin": [ { "gen": { "height": 1148151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "565cf7f9ed4efa5120060905f152234cc28b1474d952b20bd33bda5ac35d1304" } } ], "extra": [ 1, 144, 175, 3, 122, 14, 234, 123, 244, 16, 225, 29, 44, 38, 6, 181, 189, 58, 160, 61, 114, 12, 99, 88, 137, 24, 193, 5, 143, 58, 237, 163, 238, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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