Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25b5be16289bd707b9217f23fe2ef03dc6eda57abecd6ad9dd2444bde70e3b7c

Tx prefix hash: 5c7e4ef2a8ac55394c30dd30ba4a0f03c1482abe4e9b6a7946334ca531f28b8e
Tx public key: dd7afeedf39d7f43b43fb245c53a71a3b1af3b50da565174c35776ff2d8fc93f
Timestamp: 1746123556 Timestamp [UCT]: 2025-05-01 18:19:16 Age [y:d:h:m:s]: 00:204:05:05:05
Block: 1273606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143669 RingCT/type: yes/0
Extra: 01dd7afeedf39d7f43b43fb245c53a71a3b1af3b50da565174c35776ff2d8fc93f0211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bab44a85b6c9c1075999838c0e4b330000f0325170f5ca802670b8165ad2a2b 0.600000000000 1760889 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": 1273616, "vin": [ { "gen": { "height": 1273606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bab44a85b6c9c1075999838c0e4b330000f0325170f5ca802670b8165ad2a2b" } } ], "extra": [ 1, 221, 122, 254, 237, 243, 157, 127, 67, 180, 63, 178, 69, 197, 58, 113, 163, 177, 175, 59, 80, 218, 86, 81, 116, 195, 87, 118, 255, 45, 143, 201, 63, 2, 17, 0, 0, 0, 3, 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