Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25e0c7739a88e642558444e1a20a2d528b992eb3dd40d3d499599f31a2cea062

Tx prefix hash: 5fd231e4c1893b42552b14a4b90a5987497a1b5501738a7ba926769706a69f5a
Tx public key: 72c0b58470e78c16ca091a2f97a8c5ca7507f4ef8028fa3022d9675b19faee76
Timestamp: 1753015229 Timestamp [UCT]: 2025-07-20 12:40:29 Age [y:d:h:m:s]: 00:112:03:53:28
Block: 1329523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78969 RingCT/type: yes/0
Extra: 0172c0b58470e78c16ca091a2f97a8c5ca7507f4ef8028fa3022d9675b19faee76021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d4ad27026aac35deac3c2176e33e65605f25d7c083692e3387dd4eaa96d6450 0.600000000000 1817300 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": 1329533, "vin": [ { "gen": { "height": 1329523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d4ad27026aac35deac3c2176e33e65605f25d7c083692e3387dd4eaa96d6450" } } ], "extra": [ 1, 114, 192, 181, 132, 112, 231, 140, 22, 202, 9, 26, 47, 151, 168, 197, 202, 117, 7, 244, 239, 128, 40, 250, 48, 34, 217, 103, 91, 25, 250, 238, 118, 2, 17, 0, 0, 0, 6, 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