Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96fb6cb5e79859a19776aa60f030e48c1ec1febbd227d19666f4cbbbd56dd437

Tx prefix hash: 938e01eff1f0618e0e99199706cf050a291fee36ae550b9ad77a223e5e9442c0
Tx public key: 471512df91620d6d4c7a25a0f80fdba9a472f89fe85ad2d860507ad1ddd223df
Timestamp: 1740786617 Timestamp [UCT]: 2025-02-28 23:50:17 Age [y:d:h:m:s]: 00:012:08:59:44
Block: 1229418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8884 RingCT/type: yes/0
Extra: 01471512df91620d6d4c7a25a0f80fdba9a472f89fe85ad2d860507ad1ddd223df021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bad1d0df5c59d778db26600ba859dc6ee7247306fa83f5add7dba79be555cac6 0.600000000000 1716305 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": 1229428, "vin": [ { "gen": { "height": 1229418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bad1d0df5c59d778db26600ba859dc6ee7247306fa83f5add7dba79be555cac6" } } ], "extra": [ 1, 71, 21, 18, 223, 145, 98, 13, 109, 76, 122, 37, 160, 248, 15, 219, 169, 164, 114, 248, 159, 232, 90, 210, 216, 96, 80, 122, 209, 221, 210, 35, 223, 2, 17, 0, 0, 0, 4, 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