Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 548add9bcad3f05d970174a022ac8f5919d97bfe93fcb3965f039faa051e9651

Tx prefix hash: cfb6528ee1d320352b63d71e50bf11261d50f01920f038ccd6e8e46f035dad7d
Tx public key: 64f53ae2bd79910e42a2d5516a29ffacc44c58a8b7a9a4a93cafacab0848dca2
Timestamp: 1751825814 Timestamp [UCT]: 2025-07-06 18:16:54 Age [y:d:h:m:s]: 00:135:19:51:39
Block: 1320088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95482 RingCT/type: yes/0
Extra: 0164f53ae2bd79910e42a2d5516a29ffacc44c58a8b7a9a4a93cafacab0848dca2021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7268c10188ef8a590cf0971c2dcfc2e755d6388eae00c61357197cdcba3c491a 0.600000000000 1807783 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": 1320098, "vin": [ { "gen": { "height": 1320088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7268c10188ef8a590cf0971c2dcfc2e755d6388eae00c61357197cdcba3c491a" } } ], "extra": [ 1, 100, 245, 58, 226, 189, 121, 145, 14, 66, 162, 213, 81, 106, 41, 255, 172, 196, 76, 88, 168, 183, 169, 164, 169, 60, 175, 172, 171, 8, 72, 220, 162, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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