Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb7b0145a1d3042874be869be132f099d9ce9802c07fe6591c07e66e6c4c0a23

Tx prefix hash: 32f2ec3004b7c121a31cabbbba866c0a992b411cd4cfdb834978200af7076312
Tx public key: 7398b4f9ba65f0320d0dfd1f18e03de5ed3532404cffbc1fc2ee4b2e577c7a54
Timestamp: 1698459899 Timestamp [UCT]: 2023-10-28 02:24:59 Age [y:d:h:m:s]: 01:231:03:18:06
Block: 879197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426134 RingCT/type: yes/0
Extra: 017398b4f9ba65f0320d0dfd1f18e03de5ed3532404cffbc1fc2ee4b2e577c7a5402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.749644538000 dcy

stealth address amount amount idx
00: 2afad9432ea0e537b99c6a16733051456e395376f9547851df449eac1de2162d 0.749644538000 1334701 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": 879207, "vin": [ { "gen": { "height": 879197 } } ], "vout": [ { "amount": 749644538, "target": { "key": "2afad9432ea0e537b99c6a16733051456e395376f9547851df449eac1de2162d" } } ], "extra": [ 1, 115, 152, 180, 249, 186, 101, 240, 50, 13, 13, 253, 31, 24, 224, 61, 229, 237, 53, 50, 64, 76, 255, 188, 31, 194, 238, 75, 46, 87, 124, 122, 84, 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