Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 289e67c5deaede2efad6b544de9c3aa180852791807cc434ffd5873a6b016f8e

Tx prefix hash: a3181860ed1a6f0628114a5c6de3de9aa94a04886e9f48034e1dfc5b0553f4d0
Tx public key: e49d452747491097e11712782f69d0c7f12eed92338a112b3b1511a79f7dc88f
Timestamp: 1734880613 Timestamp [UCT]: 2024-12-22 15:16:53 Age [y:d:h:m:s]: 00:103:01:06:19
Block: 1180827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73415 RingCT/type: yes/0
Extra: 01e49d452747491097e11712782f69d0c7f12eed92338a112b3b1511a79f7dc88f021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d92b1836d332c69a11b5fea7dfd7e743907a3d9fcd59aac44ccaec2de033be2 0.600000000000 1667242 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": 1180837, "vin": [ { "gen": { "height": 1180827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d92b1836d332c69a11b5fea7dfd7e743907a3d9fcd59aac44ccaec2de033be2" } } ], "extra": [ 1, 228, 157, 69, 39, 71, 73, 16, 151, 225, 23, 18, 120, 47, 105, 208, 199, 241, 46, 237, 146, 51, 138, 17, 43, 59, 21, 17, 167, 159, 125, 200, 143, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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