Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59027c9cbc252907d5eed13757b3748335bf31d8e0cba53441f19e44eef73683

Tx prefix hash: acefd0a239cf0faa83ad8852f2e1e5aa47a90a1fde6371123ef5436ad6dff5ea
Tx public key: 9044b579927e1f4a64799f1d9c154029f896d9729e7f4b65a618ab4cf35dc893
Timestamp: 1740326369 Timestamp [UCT]: 2025-02-23 15:59:29 Age [y:d:h:m:s]: 00:226:13:00:44
Block: 1225599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159618 RingCT/type: yes/0
Extra: 019044b579927e1f4a64799f1d9c154029f896d9729e7f4b65a618ab4cf35dc89302110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 317239e6ebc405a940344e384c2bc0612c9ed28d02f204bfaad2c50286c07195 0.600000000000 1712466 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": 1225609, "vin": [ { "gen": { "height": 1225599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "317239e6ebc405a940344e384c2bc0612c9ed28d02f204bfaad2c50286c07195" } } ], "extra": [ 1, 144, 68, 181, 121, 146, 126, 31, 74, 100, 121, 159, 29, 156, 21, 64, 41, 248, 150, 217, 114, 158, 127, 75, 101, 166, 24, 171, 76, 243, 93, 200, 147, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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