Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d50a5851dab4447e376fef4f2382bb8d248d32a0fc8156517397758d6d324e0

Tx prefix hash: 926eb3fdf8c1f86659f0f175999ea3611c5113bd1d46cb9ad93e4fe84f278da0
Tx public key: 3d58557c2d7dc06c3ab9a4496ab2002d2a118396df0dcfb9419004dcce90277d
Timestamp: 1715274776 Timestamp [UCT]: 2024-05-09 17:12:56 Age [y:d:h:m:s]: 00:189:01:13:59
Block: 1018386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135319 RingCT/type: yes/0
Extra: 013d58557c2d7dc06c3ab9a4496ab2002d2a118396df0dcfb9419004dcce90277d0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4303f526b033f057dc0d03f9d40e90275440ac27e5595af280d368f146bb73d 0.600000000000 1482175 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": 1018396, "vin": [ { "gen": { "height": 1018386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4303f526b033f057dc0d03f9d40e90275440ac27e5595af280d368f146bb73d" } } ], "extra": [ 1, 61, 88, 85, 124, 45, 125, 192, 108, 58, 185, 164, 73, 106, 178, 0, 45, 42, 17, 131, 150, 223, 13, 207, 185, 65, 144, 4, 220, 206, 144, 39, 125, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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