Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 685821d494409da56476588f60da9f49e89bed63e96fcc51e2af851adc809b49

Tx prefix hash: 7fa340da7055f852a2565ab64e976cf60b0f9b4f7197b4973e8f612daffed76b
Tx public key: e3a5945d8c883d59e8119034ea52338dc1d8e1d4c7de9c79adb739c2f2fab511
Timestamp: 1740837263 Timestamp [UCT]: 2025-03-01 13:54:23 Age [y:d:h:m:s]: 00:264:17:52:19
Block: 1229840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186960 RingCT/type: yes/0
Extra: 01e3a5945d8c883d59e8119034ea52338dc1d8e1d4c7de9c79adb739c2f2fab511021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e707ddeba36a8293e3c986352dba5c90d2a578898d56a7d4099a727724920cf2 0.600000000000 1716731 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": 1229850, "vin": [ { "gen": { "height": 1229840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e707ddeba36a8293e3c986352dba5c90d2a578898d56a7d4099a727724920cf2" } } ], "extra": [ 1, 227, 165, 148, 93, 140, 136, 61, 89, 232, 17, 144, 52, 234, 82, 51, 141, 193, 216, 225, 212, 199, 222, 156, 121, 173, 183, 57, 194, 242, 250, 181, 17, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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