Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bd99ae8889768331fa13f6b0110f3c01e42c80b93a0d5aedc59e9e9a1cf1fc1

Tx prefix hash: d6e0aab75e916d24037e0e46ddaebfbbff715834c838a8f235a6f458493eb1b9
Tx public key: dbd1e52dae6d2bb8dcc36ec0a068b7b8e72be11ad893dd83f172e868837e62e4
Timestamp: 1706711261 Timestamp [UCT]: 2024-01-31 14:27:41 Age [y:d:h:m:s]: 01:075:16:24:55
Block: 947368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315175 RingCT/type: yes/0
Extra: 01dbd1e52dae6d2bb8dcc36ec0a068b7b8e72be11ad893dd83f172e868837e62e402110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72e28096922f3013866eaaa0e274848625b5e7919d5f64da2c353fc86ce0accb 0.600000000000 1405716 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": 947378, "vin": [ { "gen": { "height": 947368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72e28096922f3013866eaaa0e274848625b5e7919d5f64da2c353fc86ce0accb" } } ], "extra": [ 1, 219, 209, 229, 45, 174, 109, 43, 184, 220, 195, 110, 192, 160, 104, 183, 184, 231, 43, 225, 26, 216, 147, 221, 131, 241, 114, 232, 104, 131, 126, 98, 228, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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