Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8213a3ff112f0df5b32ad49e96583202ebc5ec3ed515a5a05c85d8f2e558eacb

Tx prefix hash: e401d28ae1d9cab194d416035af3ca672e8a98846f5d094ff94ea93bc5b47689
Tx public key: f514e7aeec36b0f889a86ff83cf95037020a6c0bb4e8858e30105fa5e3713197
Timestamp: 1756920858 Timestamp [UCT]: 2025-09-03 17:34:18 Age [y:d:h:m:s]: 00:111:02:40:58
Block: 1360607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79488 RingCT/type: yes/0
Extra: 01f514e7aeec36b0f889a86ff83cf95037020a6c0bb4e8858e30105fa5e3713197021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d719e40ecd5b24321fd2ea3cc9f6a994a786c526fdc7a254518087586f698ccc 0.600000000000 1848620 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": 1360617, "vin": [ { "gen": { "height": 1360607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d719e40ecd5b24321fd2ea3cc9f6a994a786c526fdc7a254518087586f698ccc" } } ], "extra": [ 1, 245, 20, 231, 174, 236, 54, 176, 248, 137, 168, 111, 248, 60, 249, 80, 55, 2, 10, 108, 11, 180, 232, 133, 142, 48, 16, 95, 165, 227, 113, 49, 151, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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