Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4294b95e12a9f7307116fa1cab61c2d1d58dad3c4123fe3c073c5022c5c4e29c

Tx prefix hash: 03bfd59f46a615680b2276f596a6e3ee908720ed573ee716084415d92eb2754e
Tx public key: 248a5ca2416967a507ae44c88a96b51d77bbc18a4a96b9570ccab3ca4b59e8dd
Timestamp: 1735062534 Timestamp [UCT]: 2024-12-24 17:48:54 Age [y:d:h:m:s]: 00:037:10:16:42
Block: 1182328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26493 RingCT/type: yes/0
Extra: 01248a5ca2416967a507ae44c88a96b51d77bbc18a4a96b9570ccab3ca4b59e8dd021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd0c4f26ee4f2ddd871985e0bee34487b9c977bf2496f46d1bfa17c88dd94602 0.600000000000 1668761 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": 1182338, "vin": [ { "gen": { "height": 1182328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd0c4f26ee4f2ddd871985e0bee34487b9c977bf2496f46d1bfa17c88dd94602" } } ], "extra": [ 1, 36, 138, 92, 162, 65, 105, 103, 165, 7, 174, 68, 200, 138, 150, 181, 29, 119, 187, 193, 138, 74, 150, 185, 87, 12, 202, 179, 202, 75, 89, 232, 221, 2, 17, 0, 0, 0, 5, 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