Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a16517bdb70c9a3e75bb6308b049115c7f55028f1d977d0ac816147987b3dc87

Tx prefix hash: de8ec560a0201ad5451adf5c09f425d59ffe90fd01148b4b343b1e87614022f4
Tx public key: e9801102402f10acbcf7b3fec0baaa968a9c79a3e358d081f202f52b3f248fcb
Timestamp: 1731186729 Timestamp [UCT]: 2024-11-09 21:12:09 Age [y:d:h:m:s]: 01:004:16:28:42
Block: 1150217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261761 RingCT/type: yes/0
Extra: 01e9801102402f10acbcf7b3fec0baaa968a9c79a3e358d081f202f52b3f248fcb021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06b1dc59c0140b68cebfbdbf503661e1d44f38fbdcfee3a80d0b448304b04a1e 0.600000000000 1635462 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": 1150227, "vin": [ { "gen": { "height": 1150217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06b1dc59c0140b68cebfbdbf503661e1d44f38fbdcfee3a80d0b448304b04a1e" } } ], "extra": [ 1, 233, 128, 17, 2, 64, 47, 16, 172, 188, 247, 179, 254, 192, 186, 170, 150, 138, 156, 121, 163, 227, 88, 208, 129, 242, 2, 245, 43, 63, 36, 143, 203, 2, 17, 0, 0, 0, 1, 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