Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a97f41196c49661099a39bbd6dc55e6c5f374e7a0c7806999bd137a097d5423

Tx prefix hash: dd68d1a272b4f8c66833dfb88fece3c12bef94d99c1a15d0c8858129c5cbe1d2
Tx public key: e2f30f5c9b2386ef82e109b4e8e48ea0fe77cea120aafcda173707b022aa9421
Timestamp: 1741296301 Timestamp [UCT]: 2025-03-06 21:25:01 Age [y:d:h:m:s]: 00:260:02:56:59
Block: 1233648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183659 RingCT/type: yes/0
Extra: 01e2f30f5c9b2386ef82e109b4e8e48ea0fe77cea120aafcda173707b022aa94210211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb83c0c34a3aa9ac974c6e27dae05aa032e9230c4a79c3c83d2012f031e79e6f 0.600000000000 1720571 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": 1233658, "vin": [ { "gen": { "height": 1233648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb83c0c34a3aa9ac974c6e27dae05aa032e9230c4a79c3c83d2012f031e79e6f" } } ], "extra": [ 1, 226, 243, 15, 92, 155, 35, 134, 239, 130, 225, 9, 180, 232, 228, 142, 160, 254, 119, 206, 161, 32, 170, 252, 218, 23, 55, 7, 176, 34, 170, 148, 33, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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