Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9293e47c4113de6a4705f7dd69966bb13fb6f41e147e0c763eb663d0f503616d

Tx prefix hash: 414116252952a7c87c2d837b530089cc6e27b94143f0b349705f875775d4f30c
Tx public key: f6c44f12e185a9e1b9e214e3ef1abc9781c94ecd1e8ebc162cdf0f74d0eeeee9
Timestamp: 1583531272 Timestamp [UCT]: 2020-03-06 21:47:52 Age [y:d:h:m:s]: 04:299:22:27:53
Block: 77651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1109017 RingCT/type: yes/0
Extra: 01f6c44f12e185a9e1b9e214e3ef1abc9781c94ecd1e8ebc162cdf0f74d0eeeee902110000000481a90efe000000000000000000

1 output(s) for total of 339.399185636000 dcy

stealth address amount amount idx
00: cca5cc0926102e73a656a4a6d9b0f73badd9be94f85a4b1eac286474afc97de5 339.399185636000 142812 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": 77661, "vin": [ { "gen": { "height": 77651 } } ], "vout": [ { "amount": 339399185636, "target": { "key": "cca5cc0926102e73a656a4a6d9b0f73badd9be94f85a4b1eac286474afc97de5" } } ], "extra": [ 1, 246, 196, 79, 18, 225, 133, 169, 225, 185, 226, 20, 227, 239, 26, 188, 151, 129, 201, 78, 205, 30, 142, 188, 22, 44, 223, 15, 116, 208, 238, 238, 233, 2, 17, 0, 0, 0, 4, 129, 169, 14, 254, 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