Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 652d61f8f5c29147c583c80ae56fd95e7dde4594e8f914236be17cfe56c5f407

Tx prefix hash: a693c0b3e2ac823cc5f318547f4a95c1c989695503004fb04b8dcd75e7c55a44
Tx public key: e83e3deb2074ddcf065eecffd10638e442e60de4a20116ff12eacb15939082bf
Timestamp: 1681453091 Timestamp [UCT]: 2023-04-14 06:18:11 Age [y:d:h:m:s]: 01:317:21:28:23
Block: 738219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488453 RingCT/type: yes/0
Extra: 01e83e3deb2074ddcf065eecffd10638e442e60de4a20116ff12eacb15939082bf021100000003b3164c24000000000000000000

1 output(s) for total of 2.197729431000 dcy

stealth address amount amount idx
00: 79bf4ad9626f677b0202a4754ac7afd475b3be1ae3aae6b4115d2ebb5e60d5e8 2.197729431000 1184880 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": 738229, "vin": [ { "gen": { "height": 738219 } } ], "vout": [ { "amount": 2197729431, "target": { "key": "79bf4ad9626f677b0202a4754ac7afd475b3be1ae3aae6b4115d2ebb5e60d5e8" } } ], "extra": [ 1, 232, 62, 61, 235, 32, 116, 221, 207, 6, 94, 236, 255, 209, 6, 56, 228, 66, 230, 13, 228, 162, 1, 22, 255, 18, 234, 203, 21, 147, 144, 130, 191, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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