Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55ce088e6dbafd88f527329c0570e99a1b36841832df86876235eccb1a341c69

Tx prefix hash: c4edda823c036668740ea6262e39fbddc88c7e38aeb17a74baa7344e0a146047
Tx public key: ac460f6c09eac22e9ac01312f80ee87cb4cfe770ef49a9fc8a5bf41ade4dcfab
Timestamp: 1760885328 Timestamp [UCT]: 2025-10-19 14:48:48 Age [y:d:h:m:s]: 00:105:06:30:43
Block: 1393417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75176 RingCT/type: yes/0
Extra: 01ac460f6c09eac22e9ac01312f80ee87cb4cfe770ef49a9fc8a5bf41ade4dcfab02110000000825a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba6e9656989fba7f322c00a3209d6fa7caf9ae327efedda93fc0c3f657104d77 0.600000000000 1881682 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": 1393427, "vin": [ { "gen": { "height": 1393417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba6e9656989fba7f322c00a3209d6fa7caf9ae327efedda93fc0c3f657104d77" } } ], "extra": [ 1, 172, 70, 15, 108, 9, 234, 194, 46, 154, 192, 19, 18, 248, 14, 232, 124, 180, 207, 231, 112, 239, 73, 169, 252, 138, 91, 244, 26, 222, 77, 207, 171, 2, 17, 0, 0, 0, 8, 37, 163, 90, 15, 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