Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a2cbca74c5f490b23b7fb801c69833caccdaed90552d8aea0e3bffe0a5c9484

Tx prefix hash: b6077f1167f3533b85fbb0d5a1dec9dd53de84f9e5fb5886cd0c2d6109bb581a
Tx public key: 10776ee762e86ca50ce6dc0e98e89099bcec75d829c556178b574ad13e29576f
Timestamp: 1647566397 Timestamp [UCT]: 2022-03-18 01:19:57 Age [y:d:h:m:s]: 02:280:23:32:20
Block: 460763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 720362 RingCT/type: yes/0
Extra: 0110776ee762e86ca50ce6dc0e98e89099bcec75d829c556178b574ad13e29576f021100000005d3fcec30000000000000000000

1 output(s) for total of 18.251609663000 dcy

stealth address amount amount idx
00: ef3d21df3bf505e2b4fc9c126b5011b666a3e8e9ce9fc310e70836c3100e84f1 18.251609663000 877848 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": 460773, "vin": [ { "gen": { "height": 460763 } } ], "vout": [ { "amount": 18251609663, "target": { "key": "ef3d21df3bf505e2b4fc9c126b5011b666a3e8e9ce9fc310e70836c3100e84f1" } } ], "extra": [ 1, 16, 119, 110, 231, 98, 232, 108, 165, 12, 230, 220, 14, 152, 232, 144, 153, 188, 236, 117, 216, 41, 197, 86, 23, 139, 87, 74, 209, 62, 41, 87, 111, 2, 17, 0, 0, 0, 5, 211, 252, 236, 48, 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