Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9a040ea4c1f699a18537dd56233a8b5fb4f2bf5f6402a1ad016106c84ba5dbf

Tx prefix hash: fc07f9d923bcfe4cd34a328c2e077000401bdd71845ea4a8af6909e275c3aa6a
Tx public key: ce0cce2499dd939a921dc12a3875ca8d09d1b20472837b3df05fac7647fcf2ab
Timestamp: 1737751026 Timestamp [UCT]: 2025-01-24 20:37:06 Age [y:d:h:m:s]: 00:143:19:38:05
Block: 1204514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102543 RingCT/type: yes/0
Extra: 01ce0cce2499dd939a921dc12a3875ca8d09d1b20472837b3df05fac7647fcf2ab021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd5bf48c4c8656e0c985cd6816a79f349b8833bfddbcb9861d2ddf95d46e23af 0.600000000000 1691201 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": 1204524, "vin": [ { "gen": { "height": 1204514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd5bf48c4c8656e0c985cd6816a79f349b8833bfddbcb9861d2ddf95d46e23af" } } ], "extra": [ 1, 206, 12, 206, 36, 153, 221, 147, 154, 146, 29, 193, 42, 56, 117, 202, 141, 9, 209, 178, 4, 114, 131, 123, 61, 240, 95, 172, 118, 71, 252, 242, 171, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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