Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 424a110c576a96dd45948ad5682deaa59218615b207fc5802d3789577363a562

Tx prefix hash: dbec2a6166506017a5036da81ce5b90714fd885782f651ca5a4491175e073e5f
Tx public key: 4aa789a5c0fd8c3ea194cc078317a4b8719d7f0e585b57bd8ba02d5fdf86187f
Timestamp: 1746986002 Timestamp [UCT]: 2025-05-11 17:53:22 Age [y:d:h:m:s]: 00:183:08:35:50
Block: 1280754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128747 RingCT/type: yes/0
Extra: 014aa789a5c0fd8c3ea194cc078317a4b8719d7f0e585b57bd8ba02d5fdf86187f0211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6ecbec97c71035d2aad9832b0f4e59c587aeccf38f49e99ab9316027c42c132 0.600000000000 1768145 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": 1280764, "vin": [ { "gen": { "height": 1280754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6ecbec97c71035d2aad9832b0f4e59c587aeccf38f49e99ab9316027c42c132" } } ], "extra": [ 1, 74, 167, 137, 165, 192, 253, 140, 62, 161, 148, 204, 7, 131, 23, 164, 184, 113, 157, 127, 14, 88, 91, 87, 189, 139, 160, 45, 95, 223, 134, 24, 127, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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