Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d024e317b3abeb9b51e3f3d5c664f8dd0a1cc89123b9d3df2484736a086c88f8

Tx prefix hash: 2514f97f6cccb6f6437565f34f847f45b04258bb00a2e45ce30c0654530f1074
Tx public key: 659173feb560e44f00fedf0d4ffadf1364f90cd44cc1627e18d4eccb72a459e8
Timestamp: 1768440192 Timestamp [UCT]: 2026-01-15 01:23:12 Age [y:d:h:m:s]: 00:016:15:22:35
Block: 1455859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11880 RingCT/type: yes/0
Extra: 01659173feb560e44f00fedf0d4ffadf1364f90cd44cc1627e18d4eccb72a459e8021100000009215bbf89000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80e284810c748c80c08612331dbc716a9a572ef8e1872fa3f8d819cc077403f0 0.600000000000 1944961 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": 1455869, "vin": [ { "gen": { "height": 1455859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80e284810c748c80c08612331dbc716a9a572ef8e1872fa3f8d819cc077403f0" } } ], "extra": [ 1, 101, 145, 115, 254, 181, 96, 228, 79, 0, 254, 223, 13, 79, 250, 223, 19, 100, 249, 12, 212, 76, 193, 98, 126, 24, 212, 236, 203, 114, 164, 89, 232, 2, 17, 0, 0, 0, 9, 33, 91, 191, 137, 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