Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1c6e80fa96ea1d3d9c529e420643206e6090a96d45c24dc796bf125b0158da4

Tx prefix hash: 99ea19994c950d43c0827ae1455b1514f8c0f010152ec05a67c3a20be83336c7
Tx public key: 051374d5006197df6db3b0388f478d421c78d4e826fe34824bcae85892d2b8cb
Timestamp: 1713139322 Timestamp [UCT]: 2024-04-15 00:02:02 Age [y:d:h:m:s]: 00:341:09:04:39
Block: 1000653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244080 RingCT/type: yes/0
Extra: 01051374d5006197df6db3b0388f478d421c78d4e826fe34824bcae85892d2b8cb02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4ccc1fbf976e374433b9349219f46a0320d180c8c3583b7df89b2b5eb75c795 0.600000000000 1461151 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": 1000663, "vin": [ { "gen": { "height": 1000653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4ccc1fbf976e374433b9349219f46a0320d180c8c3583b7df89b2b5eb75c795" } } ], "extra": [ 1, 5, 19, 116, 213, 0, 97, 151, 223, 109, 179, 176, 56, 143, 71, 141, 66, 28, 120, 212, 232, 38, 254, 52, 130, 75, 202, 232, 88, 146, 210, 184, 203, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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