Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72ff0606880aec7f7759a11a0d7105cb54dd08ad48fd0249a1e5b4ddbd55b02d

Tx prefix hash: 0972c51134d247f4fa56cee5ceabdcf4c8e8764769639cb69a6a6c6cf91ddf99
Tx public key: 921abd13b074cda8ffa293469f3bfb7cb172c6f50dbe9450e5e60e67fb179add
Timestamp: 1727833771 Timestamp [UCT]: 2024-10-02 01:49:31 Age [y:d:h:m:s]: 00:257:00:47:18
Block: 1122512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183441 RingCT/type: yes/0
Extra: 01921abd13b074cda8ffa293469f3bfb7cb172c6f50dbe9450e5e60e67fb179add021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b73e3aadb4c4f0aef9e2ff44992df6b255008e2fe5954bfebd20d80abaa00f4b 0.600000000000 1604963 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": 1122522, "vin": [ { "gen": { "height": 1122512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b73e3aadb4c4f0aef9e2ff44992df6b255008e2fe5954bfebd20d80abaa00f4b" } } ], "extra": [ 1, 146, 26, 189, 19, 176, 116, 205, 168, 255, 162, 147, 70, 159, 59, 251, 124, 177, 114, 198, 245, 13, 190, 148, 80, 229, 230, 14, 103, 251, 23, 154, 221, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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