Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 040b68f65753c90ba1acc5ce5bdd5b3fb3a43d35db0bb71061963d204a3cfb8e

Tx prefix hash: 03e9920ce0ce088afc4d1fa7a8715f565b99768b1a4a0162e33c27bacb46f77f
Tx public key: 0ae9cbd77358cd1929e7f6a14c4486b3da65df666369e441d135cb9902ce10ae
Timestamp: 1707214050 Timestamp [UCT]: 2024-02-06 10:07:30 Age [y:d:h:m:s]: 01:022:05:53:55
Block: 951546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276929 RingCT/type: yes/0
Extra: 010ae9cbd77358cd1929e7f6a14c4486b3da65df666369e441d135cb9902ce10ae02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1825a43c9d96152bc1b4a277a867266d5371067efd115e4876ab430eb0c40e42 0.600000000000 1410326 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": 951556, "vin": [ { "gen": { "height": 951546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1825a43c9d96152bc1b4a277a867266d5371067efd115e4876ab430eb0c40e42" } } ], "extra": [ 1, 10, 233, 203, 215, 115, 88, 205, 25, 41, 231, 246, 161, 76, 68, 134, 179, 218, 101, 223, 102, 99, 105, 228, 65, 209, 53, 203, 153, 2, 206, 16, 174, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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