Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e013f5e433522062ac22ca30d80f1ead315da95c80b66994dc7e02b0adc39fe6

Tx prefix hash: 04615c7082d64451a548f40084c4798526c0f648ff12368ecee416e49f81f32b
Tx public key: 6bc794cce82232a281d03769e1b0902aa13f9ae2882cbf6a5871cb8db25c96fe
Timestamp: 1752175043 Timestamp [UCT]: 2025-07-10 19:17:23 Age [y:d:h:m:s]: 00:166:07:05:35
Block: 1322799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117471 RingCT/type: yes/0
Extra: 016bc794cce82232a281d03769e1b0902aa13f9ae2882cbf6a5871cb8db25c96fe021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53e21017d859d07329c8cfa96fd7e9c16e809b65d96b93ca4d53b0dd3fb17e2f 0.600000000000 1810530 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": 1322809, "vin": [ { "gen": { "height": 1322799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53e21017d859d07329c8cfa96fd7e9c16e809b65d96b93ca4d53b0dd3fb17e2f" } } ], "extra": [ 1, 107, 199, 148, 204, 232, 34, 50, 162, 129, 208, 55, 105, 225, 176, 144, 42, 161, 63, 154, 226, 136, 44, 191, 106, 88, 113, 203, 141, 178, 92, 150, 254, 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