Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35a773c16ddc10e111a6cbb9855485e9ebd4fdc4f4a521f0bc216dc67708f1d8

Tx prefix hash: 60ddf997663da92b3c84692533786b31a165d2896c819d79aa76a1380796fe6b
Tx public key: 8a7536de1038e8575e8f7f55907dbab870d37a5fad1d4d6d3fac42884cec3dc6
Timestamp: 1674662535 Timestamp [UCT]: 2023-01-25 16:02:15 Age [y:d:h:m:s]: 01:251:06:23:00
Block: 682558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440558 RingCT/type: yes/0
Extra: 018a7536de1038e8575e8f7f55907dbab870d37a5fad1d4d6d3fac42884cec3dc60211000000025029cbac000000000000000000

1 output(s) for total of 3.360484848000 dcy

stealth address amount amount idx
00: aaa548302d55e215ea16e89600f875c69fb1843bce30459b0828052bd452a08d 3.360484848000 1124689 of 0

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": 682568, "vin": [ { "gen": { "height": 682558 } } ], "vout": [ { "amount": 3360484848, "target": { "key": "aaa548302d55e215ea16e89600f875c69fb1843bce30459b0828052bd452a08d" } } ], "extra": [ 1, 138, 117, 54, 222, 16, 56, 232, 87, 94, 143, 127, 85, 144, 125, 186, 184, 112, 211, 122, 95, 173, 29, 77, 109, 63, 172, 66, 136, 76, 236, 61, 198, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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