Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fbd47e80774f0ea150c8851522de48445c1991b27db3b9e54b75cf225299270

Tx prefix hash: 96ec66c0cf9f7345b13e80e65eed5e580c73128298e9d0eaa3405f82b754f89d
Tx public key: 656708429438d7fe2daa4936a4cf83a0f7add2fa92e5d00ae0e1a11658d8e0b9
Timestamp: 1703106102 Timestamp [UCT]: 2023-12-20 21:01:42 Age [y:d:h:m:s]: 01:348:20:07:27
Block: 917520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508171 RingCT/type: yes/0
Extra: 01656708429438d7fe2daa4936a4cf83a0f7add2fa92e5d00ae0e1a11658d8e0b9021100000002bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e687488c966f040f22a863614e444e7ea18658266fbc84f45f91f6a79f72d88 0.600000000000 1375102 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": 917530, "vin": [ { "gen": { "height": 917520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e687488c966f040f22a863614e444e7ea18658266fbc84f45f91f6a79f72d88" } } ], "extra": [ 1, 101, 103, 8, 66, 148, 56, 215, 254, 45, 170, 73, 54, 164, 207, 131, 160, 247, 173, 210, 250, 146, 229, 208, 10, 224, 225, 161, 22, 88, 216, 224, 185, 2, 17, 0, 0, 0, 2, 191, 162, 34, 33, 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