Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfd34f33cabc8f8c73ab7ba25eb8c8c81ce9f40169a28802988bcb4b0d6bad96

Tx prefix hash: 8d87b327acdc31a2c34d019af8cdfbaf1b028ccea95b06b3cd5e5e60754eaa1e
Tx public key: 049ee55dc7a469027aed42d0cb4d38b6374b42d24e4d61f9285a055865ce2a68
Timestamp: 1736532719 Timestamp [UCT]: 2025-01-10 18:11:59 Age [y:d:h:m:s]: 00:065:18:37:31
Block: 1194480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46803 RingCT/type: yes/0
Extra: 01049ee55dc7a469027aed42d0cb4d38b6374b42d24e4d61f9285a055865ce2a680211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1adc9ee9788ec0854d9a6f4099b43f3a3a026f35f45eda20cf0e2a262b43bf7 0.600000000000 1681051 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": 1194490, "vin": [ { "gen": { "height": 1194480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1adc9ee9788ec0854d9a6f4099b43f3a3a026f35f45eda20cf0e2a262b43bf7" } } ], "extra": [ 1, 4, 158, 229, 93, 199, 164, 105, 2, 122, 237, 66, 208, 203, 77, 56, 182, 55, 75, 66, 210, 78, 77, 97, 249, 40, 90, 5, 88, 101, 206, 42, 104, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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