Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88f7ad31409406789f9afaf79640cc181324fee0aeef243055824fc5a3256dd5

Tx prefix hash: cfdacbb7e62cdc92db4a9f527ccc4232f1f2c988010ad31fe2a63210733f9c7a
Tx public key: 9284c528c542f9b8be92c1a91bde9a9bc3aa18b77c5bbd71dc1c875a197e9269
Timestamp: 1696569321 Timestamp [UCT]: 2023-10-06 05:15:21 Age [y:d:h:m:s]: 01:146:04:35:03
Block: 863504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365493 RingCT/type: yes/0
Extra: 019284c528c542f9b8be92c1a91bde9a9bc3aa18b77c5bbd71dc1c875a197e92690211000000024b8f5122000000000000000000

1 output(s) for total of 0.844992448000 dcy

stealth address amount amount idx
00: b1fb3338d35a1c842edddedcde295775ac8f08a03d25e7fb04b625cd0ee4a9fe 0.844992448000 1317960 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": 863514, "vin": [ { "gen": { "height": 863504 } } ], "vout": [ { "amount": 844992448, "target": { "key": "b1fb3338d35a1c842edddedcde295775ac8f08a03d25e7fb04b625cd0ee4a9fe" } } ], "extra": [ 1, 146, 132, 197, 40, 197, 66, 249, 184, 190, 146, 193, 169, 27, 222, 154, 155, 195, 170, 24, 183, 124, 91, 189, 113, 220, 28, 135, 90, 25, 126, 146, 105, 2, 17, 0, 0, 0, 2, 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