Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9137624999c04ba7e9c4632fc8d2f5520d19a6350d63006435617f80cda5c23e

Tx prefix hash: 4faf3644adc501e68c8a9477a8bcfb732410c74cd3ddd527414265c8e6a51ddb
Tx public key: c221fd871b60fa0553344fde6691dc08d3b47a7ce15d890fecde2b7da974634c
Timestamp: 1749709300 Timestamp [UCT]: 2025-06-12 06:21:40 Age [y:d:h:m:s]: 00:150:04:10:02
Block: 1303267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105036 RingCT/type: yes/0
Extra: 01c221fd871b60fa0553344fde6691dc08d3b47a7ce15d890fecde2b7da974634c021100000007bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 678189e4d036d23359332729c5a3cc83cf96af3f951c6495f803aca5e614dfd8 0.600000000000 1790846 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": 1303277, "vin": [ { "gen": { "height": 1303267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "678189e4d036d23359332729c5a3cc83cf96af3f951c6495f803aca5e614dfd8" } } ], "extra": [ 1, 194, 33, 253, 135, 27, 96, 250, 5, 83, 52, 79, 222, 102, 145, 220, 8, 211, 180, 122, 124, 225, 93, 137, 15, 236, 222, 43, 125, 169, 116, 99, 76, 2, 17, 0, 0, 0, 7, 191, 81, 178, 162, 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