Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc3651a524a3490096bbf18147e00754314a237f730da1301732a2252b6a43da

Tx prefix hash: b1f213cfe0dd063693e6b85ec434ea2b28018753c72aefb01525f1fd18ce8fb5
Tx public key: c6cae411cafd4f2f8177b03344d9a9a4efd9febabe3c2f67ad77b89f8bfc398c
Timestamp: 1750459564 Timestamp [UCT]: 2025-06-20 22:46:04 Age [y:d:h:m:s]: 00:152:09:32:59
Block: 1309342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106772 RingCT/type: yes/0
Extra: 01c6cae411cafd4f2f8177b03344d9a9a4efd9febabe3c2f67ad77b89f8bfc398c02110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea9126a0e40b72bd98d17177402d81aead756e7011ff191623676798a99b2e7b 0.600000000000 1796957 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": 1309352, "vin": [ { "gen": { "height": 1309342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea9126a0e40b72bd98d17177402d81aead756e7011ff191623676798a99b2e7b" } } ], "extra": [ 1, 198, 202, 228, 17, 202, 253, 79, 47, 129, 119, 176, 51, 68, 217, 169, 164, 239, 217, 254, 186, 190, 60, 47, 103, 173, 119, 184, 159, 139, 252, 57, 140, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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