Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9ee03fd0e8e0028dbe3f26c9a218e8a4af963f1c9d0c9ea82ef0e594b26513c

Tx prefix hash: 16b8798c7ccaebdc2535df2252f7e842a3a58776d756fd33f90219f3f8eb999f
Tx public key: 04d820b70201ad7e2e9419390f7ee5e9369b8250ef2ed5b6d6688c1d4dfabc5b
Timestamp: 1764065572 Timestamp [UCT]: 2025-11-25 10:12:52 Age [y:d:h:m:s]: 00:001:23:53:30
Block: 1419752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1430 RingCT/type: yes/0
Extra: 0104d820b70201ad7e2e9419390f7ee5e9369b8250ef2ed5b6d6688c1d4dfabc5b021100000003fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c17405f3d88e5a1389e2a71badda1d09824d91e363f5270f27c48907abf94df4 0.600000000000 1908293 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": 1419762, "vin": [ { "gen": { "height": 1419752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c17405f3d88e5a1389e2a71badda1d09824d91e363f5270f27c48907abf94df4" } } ], "extra": [ 1, 4, 216, 32, 183, 2, 1, 173, 126, 46, 148, 25, 57, 15, 126, 229, 233, 54, 155, 130, 80, 239, 46, 213, 182, 214, 104, 140, 29, 77, 250, 188, 91, 2, 17, 0, 0, 0, 3, 251, 143, 208, 137, 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