Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b13b9fab23d21189777706af0986697db5505247a9aeec0ec253fa4dcd2a169

Tx prefix hash: 02ec7b3b8cecbdead1bee0d4b3c00b54cb04ec94a9afa0f3a0eb8aeb3f614bab
Tx public key: 9833e4fa2144b3d161ccd9aeb0bb4cdf693c97b432996a498650ba2c13ebe903
Timestamp: 1728792410 Timestamp [UCT]: 2024-10-13 04:06:50 Age [y:d:h:m:s]: 00:152:14:57:59
Block: 1130449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108871 RingCT/type: yes/0
Extra: 019833e4fa2144b3d161ccd9aeb0bb4cdf693c97b432996a498650ba2c13ebe903021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce57f13abc6d3eec55e63c5d369345d2ccc3022a2d0a32291aeca832d9749eb0 0.600000000000 1613326 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": 1130459, "vin": [ { "gen": { "height": 1130449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce57f13abc6d3eec55e63c5d369345d2ccc3022a2d0a32291aeca832d9749eb0" } } ], "extra": [ 1, 152, 51, 228, 250, 33, 68, 179, 209, 97, 204, 217, 174, 176, 187, 76, 223, 105, 60, 151, 180, 50, 153, 106, 73, 134, 80, 186, 44, 19, 235, 233, 3, 2, 17, 0, 0, 0, 3, 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