Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 881977aadea1d7dda2e8871a51a09d792153a6e976f77811d7c7064c49a40e49

Tx prefix hash: 8fdb17b43871081e7932128605f1d52e5f07f4f5ec9434b22093c90b12f563c3
Tx public key: b0b5b4846f4b7c260c6cdbcef1887ac9bf5a46b4f105d681a08accb81b24b368
Timestamp: 1765053909 Timestamp [UCT]: 2025-12-06 20:45:09 Age [y:d:h:m:s]: 00:016:23:02:38
Block: 1427929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12145 RingCT/type: yes/0
Extra: 01b0b5b4846f4b7c260c6cdbcef1887ac9bf5a46b4f105d681a08accb81b24b368021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ada10b349714ce1296155f17b9178d10fb56b6ae252bd0da140a7e4bd2b19395 0.600000000000 1916636 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": 1427939, "vin": [ { "gen": { "height": 1427929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ada10b349714ce1296155f17b9178d10fb56b6ae252bd0da140a7e4bd2b19395" } } ], "extra": [ 1, 176, 181, 180, 132, 111, 75, 124, 38, 12, 108, 219, 206, 241, 136, 122, 201, 191, 90, 70, 180, 241, 5, 214, 129, 160, 138, 204, 184, 27, 36, 179, 104, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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