Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70e863387e3ccac65b72176eb19eafd33152620129012f9fd37894e8ddaf34ac

Tx prefix hash: 7f36a35e8e8cbc0a48f0d88f6bc89fe49ecba1c2dcdfeb8e1c64d3c4f2baaeff
Tx public key: 18ecf822b2c9648e34a0efba3ee5336843ad98a70bef7b3b162634360e5fe9ea
Timestamp: 1752688897 Timestamp [UCT]: 2025-07-16 18:01:37 Age [y:d:h:m:s]: 00:084:09:42:19
Block: 1326859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59046 RingCT/type: yes/0
Extra: 0118ecf822b2c9648e34a0efba3ee5336843ad98a70bef7b3b162634360e5fe9ea021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63c53121b508fd3252166a9c33cec8cefb9efe3e94c1f0112e26120c6e56edbc 0.600000000000 1814612 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": 1326869, "vin": [ { "gen": { "height": 1326859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63c53121b508fd3252166a9c33cec8cefb9efe3e94c1f0112e26120c6e56edbc" } } ], "extra": [ 1, 24, 236, 248, 34, 178, 201, 100, 142, 52, 160, 239, 186, 62, 229, 51, 104, 67, 173, 152, 167, 11, 239, 123, 59, 22, 38, 52, 54, 14, 95, 233, 234, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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