Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9354f6e626d2ce133f8109d2d7d76a5769c922d814cdf3425be0d68450cc4142

Tx prefix hash: 91969d11bb9121922b65dac151ce6899554c1d688d939c043a46f5b6e1f9008d
Tx public key: c4c70617029d404f96979da64801a40c2a8496e732c8fb6e173336cc76870b3f
Timestamp: 1702648843 Timestamp [UCT]: 2023-12-15 14:00:43 Age [y:d:h:m:s]: 01:036:03:13:18
Block: 913699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287151 RingCT/type: yes/0
Extra: 01c4c70617029d404f96979da64801a40c2a8496e732c8fb6e173336cc76870b3f02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d64a66cb830825c116ba355b8a301226d64922d1851b619e5df9e57a25e9028f 0.600000000000 1370975 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": 913709, "vin": [ { "gen": { "height": 913699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d64a66cb830825c116ba355b8a301226d64922d1851b619e5df9e57a25e9028f" } } ], "extra": [ 1, 196, 199, 6, 23, 2, 157, 64, 79, 150, 151, 157, 166, 72, 1, 164, 12, 42, 132, 150, 231, 50, 200, 251, 110, 23, 51, 54, 204, 118, 135, 11, 63, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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