Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 652673c1efd183a7a391d1a8ce8994be6b582c7986e5e8d7ff241b5595918962

Tx prefix hash: f85b1027979756a87fb8bee42ed22eac4df13e83989267cb7eb34efb3cb3ba00
Tx public key: a1e2707bf04ff06853b86b040dd2a3f8532ae394fdb6d033bd99aface5c87963
Timestamp: 1734716044 Timestamp [UCT]: 2024-12-20 17:34:04 Age [y:d:h:m:s]: 00:103:06:50:36
Block: 1179461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73573 RingCT/type: yes/0
Extra: 01a1e2707bf04ff06853b86b040dd2a3f8532ae394fdb6d033bd99aface5c87963021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 328133d93a5d86ac72530378938c9db8b2d681c9eb1654cc1af4f5582d80bc46 0.600000000000 1665856 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": 1179471, "vin": [ { "gen": { "height": 1179461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "328133d93a5d86ac72530378938c9db8b2d681c9eb1654cc1af4f5582d80bc46" } } ], "extra": [ 1, 161, 226, 112, 123, 240, 79, 240, 104, 83, 184, 107, 4, 13, 210, 163, 248, 83, 42, 227, 148, 253, 182, 208, 51, 189, 153, 175, 172, 229, 200, 121, 99, 2, 17, 0, 0, 0, 4, 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