Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8a076fb04a0f30ccdb91a346c5f33f43d6968b914de838913acce4387965d36

Tx prefix hash: 0773fcbfd486264831a9ce0edc3a7e2e3cfde91088b9a1bf035f989294b9dc32
Tx public key: 9dd77131c4ed3986ab431d683bc345b6627eec8b1642fb5d31cb0f07533ba5a9
Timestamp: 1764290221 Timestamp [UCT]: 2025-11-28 00:37:01 Age [y:d:h:m:s]: 00:040:11:35:57
Block: 1421616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28991 RingCT/type: yes/0
Extra: 019dd77131c4ed3986ab431d683bc345b6627eec8b1642fb5d31cb0f07533ba5a9021100000008d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02afa086c1e4de1ac4090586d2e8b8a2fc290dbb5e7ddeb380edb8e6dee22b6b 0.600000000000 1910173 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": 1421626, "vin": [ { "gen": { "height": 1421616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02afa086c1e4de1ac4090586d2e8b8a2fc290dbb5e7ddeb380edb8e6dee22b6b" } } ], "extra": [ 1, 157, 215, 113, 49, 196, 237, 57, 134, 171, 67, 29, 104, 59, 195, 69, 182, 98, 126, 236, 139, 22, 66, 251, 93, 49, 203, 15, 7, 83, 59, 165, 169, 2, 17, 0, 0, 0, 8, 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