Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd4890b6329ab05ed068fbcbc86adc1e5c1c7c23cd68095c54380af612249682

Tx prefix hash: 8e89ad4129f739e5c0e705cde56580b6d81d02b440c28155eb89e88df0cc8d85
Tx public key: aeee14c70bf86931c012847344c7baf5e85aabe3aa9ab1844c9f10fee6d1065a
Timestamp: 1721315021 Timestamp [UCT]: 2024-07-18 15:03:41 Age [y:d:h:m:s]: 01:118:14:13:41
Block: 1068473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343260 RingCT/type: yes/0
Extra: 01aeee14c70bf86931c012847344c7baf5e85aabe3aa9ab1844c9f10fee6d1065a02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f2da785cf244eaf05ae682f6f5e098d1edf0054f91e80d01a04d730972a8361 0.600000000000 1539552 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": 1068483, "vin": [ { "gen": { "height": 1068473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f2da785cf244eaf05ae682f6f5e098d1edf0054f91e80d01a04d730972a8361" } } ], "extra": [ 1, 174, 238, 20, 199, 11, 248, 105, 49, 192, 18, 132, 115, 68, 199, 186, 245, 232, 90, 171, 227, 170, 154, 177, 132, 76, 159, 16, 254, 230, 209, 6, 90, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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