Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6f5b121b97aa5856be648f2a0f95fe924b3f64d307589da4504f6268f5662e9

Tx prefix hash: 58c8672c180d8234aaa7218049b960c30569337b86f605ee2a9d96cd08cee58f
Tx public key: 193e2dfebe4eecd6f57707c6bdb06f72ec4dcd33ff8de0662f3d5f360048ac1a
Timestamp: 1704029763 Timestamp [UCT]: 2023-12-31 13:36:03 Age [y:d:h:m:s]: 01:282:14:44:36
Block: 925150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460776 RingCT/type: yes/0
Extra: 01193e2dfebe4eecd6f57707c6bdb06f72ec4dcd33ff8de0662f3d5f360048ac1a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a3d89eb2398e18f5374a43b9407fd89d1a2518fb0c3fef03dd9a50455ab5987 0.600000000000 1382910 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": 925160, "vin": [ { "gen": { "height": 925150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a3d89eb2398e18f5374a43b9407fd89d1a2518fb0c3fef03dd9a50455ab5987" } } ], "extra": [ 1, 25, 62, 45, 254, 190, 78, 236, 214, 245, 119, 7, 198, 189, 176, 111, 114, 236, 77, 205, 51, 255, 141, 224, 102, 47, 61, 95, 54, 0, 72, 172, 26, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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