Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b1a9011a20e209af56e84347dc659e206f2d585170c78e1ce26f02d8b5d631e

Tx prefix hash: 4cb9993d35de16f72f828c2f1232c81604c46a78677c2cae6142ba2476c7cf22
Tx public key: c5a5fd53f5ef003c6c4dfd3c2ace1ffc8e1cdc0ee4762444d522cbedd811874a
Timestamp: 1727914305 Timestamp [UCT]: 2024-10-03 00:11:45 Age [y:d:h:m:s]: 00:056:10:07:19
Block: 1123173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40312 RingCT/type: yes/0
Extra: 01c5a5fd53f5ef003c6c4dfd3c2ace1ffc8e1cdc0ee4762444d522cbedd811874a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa793e65fd5d8de026c4e4e7fc81c50aebd0001415e5c38947114571ad2cfb2d 0.600000000000 1605706 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": 1123183, "vin": [ { "gen": { "height": 1123173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa793e65fd5d8de026c4e4e7fc81c50aebd0001415e5c38947114571ad2cfb2d" } } ], "extra": [ 1, 197, 165, 253, 83, 245, 239, 0, 60, 108, 77, 253, 60, 42, 206, 31, 252, 142, 28, 220, 14, 228, 118, 36, 68, 213, 34, 203, 237, 216, 17, 135, 74, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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