Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae382a51be2ec36c75861f83da305f6a8881c0e6754cb880063b882cd028c09a

Tx prefix hash: f2db34b93d23aa7b5e0ef0645de50494fdfb8684d90d5940ec625123ec8105e3
Tx public key: dd70d5c6bb5982af37e524ac38fc2535e189e8373bf499b5abe7de56a82476ae
Timestamp: 1701614401 Timestamp [UCT]: 2023-12-03 14:40:01 Age [y:d:h:m:s]: 01:364:22:14:53
Block: 905127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519718 RingCT/type: yes/0
Extra: 01dd70d5c6bb5982af37e524ac38fc2535e189e8373bf499b5abe7de56a82476ae0211000000014b8f5122000000000000000000

1 output(s) for total of 0.615089749000 dcy

stealth address amount amount idx
00: 4696689247d09abc3bbbeb72b81a4210a20735dc0eaa60ee53e71aecbb46d0e1 0.615089749000 1361998 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": 905137, "vin": [ { "gen": { "height": 905127 } } ], "vout": [ { "amount": 615089749, "target": { "key": "4696689247d09abc3bbbeb72b81a4210a20735dc0eaa60ee53e71aecbb46d0e1" } } ], "extra": [ 1, 221, 112, 213, 198, 187, 89, 130, 175, 55, 229, 36, 172, 56, 252, 37, 53, 225, 137, 232, 55, 59, 244, 153, 181, 171, 231, 222, 86, 168, 36, 118, 174, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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