Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 624d84845fc41de6253c2da326dc5c2616a23bd5bb34975b496e40f5bcc8f418

Tx prefix hash: b3708516d13f18e98e057b253ad7a9379dbbec66a02cf11a1d186bf774e61370
Tx public key: 35c67278da527b5e3a4c46f23687d022d1c2578aafe7603ce1c54d4c486fdc64
Timestamp: 1755882798 Timestamp [UCT]: 2025-08-22 17:13:18 Age [y:d:h:m:s]: 00:090:22:17:00
Block: 1352123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64910 RingCT/type: yes/0
Extra: 0135c67278da527b5e3a4c46f23687d022d1c2578aafe7603ce1c54d4c486fdc640211000000072609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bae89845e5e71e5d73a63dd62d339e46f57a6a17188c1723350b49100bc84a4 0.600000000000 1840084 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": 1352133, "vin": [ { "gen": { "height": 1352123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bae89845e5e71e5d73a63dd62d339e46f57a6a17188c1723350b49100bc84a4" } } ], "extra": [ 1, 53, 198, 114, 120, 218, 82, 123, 94, 58, 76, 70, 242, 54, 135, 208, 34, 209, 194, 87, 138, 175, 231, 96, 60, 225, 197, 77, 76, 72, 111, 220, 100, 2, 17, 0, 0, 0, 7, 38, 9, 179, 160, 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