Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 033fd2bb09d2335df54a36361dfb00e966577ce6d37642d320eb0e86e9243c10

Tx prefix hash: 2cbca49d5cee5e6e004b8b3d6ebdc2725fe29a2485572ae87a7f2424e0036b7f
Tx public key: d42a2f1a9e1dd3e7d1c58a8e891b081f5fc3dac556fb5862f9f167cfc6522263
Timestamp: 1651704592 Timestamp [UCT]: 2022-05-04 22:49:52 Age [y:d:h:m:s]: 02:357:14:00:56
Block: 494428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 775452 RingCT/type: yes/0
Extra: 01d42a2f1a9e1dd3e7d1c58a8e891b081f5fc3dac556fb5862f9f167cfc6522263021100000008c9067537000000000000000000

1 output(s) for total of 14.117409191000 dcy

stealth address amount amount idx
00: 01c47248aba9a4a49bb9ef987dc646180d33165e08bc22a5d467ce6c3bce7f87 14.117409191000 918081 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": 494438, "vin": [ { "gen": { "height": 494428 } } ], "vout": [ { "amount": 14117409191, "target": { "key": "01c47248aba9a4a49bb9ef987dc646180d33165e08bc22a5d467ce6c3bce7f87" } } ], "extra": [ 1, 212, 42, 47, 26, 158, 29, 211, 231, 209, 197, 138, 142, 137, 27, 8, 31, 95, 195, 218, 197, 86, 251, 88, 98, 249, 241, 103, 207, 198, 82, 34, 99, 2, 17, 0, 0, 0, 8, 201, 6, 117, 55, 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