Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 541be98ece2648251fac1260cd3537d7cad90966cb44d9f920063ee2a9561c2e

Tx prefix hash: 334fa797a6f9c95516436b58c1c3c08db0b56b6fb8bf793ee63ec233cbc6d7bc
Tx public key: d29706b87d01c364601cd4bb4ec8016359b256e2f4e801e403dbf22bc1a0c0a9
Timestamp: 1726951589 Timestamp [UCT]: 2024-09-21 20:46:29 Age [y:d:h:m:s]: 00:173:19:12:31
Block: 1115191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124039 RingCT/type: yes/0
Extra: 01d29706b87d01c364601cd4bb4ec8016359b256e2f4e801e403dbf22bc1a0c0a9021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fa4227b8cbebe01fd654923a0d56b35cfade82791638f1b337f1e721d313261 0.600000000000 1595238 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": 1115201, "vin": [ { "gen": { "height": 1115191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fa4227b8cbebe01fd654923a0d56b35cfade82791638f1b337f1e721d313261" } } ], "extra": [ 1, 210, 151, 6, 184, 125, 1, 195, 100, 96, 28, 212, 187, 78, 200, 1, 99, 89, 178, 86, 226, 244, 232, 1, 228, 3, 219, 242, 43, 193, 160, 192, 169, 2, 17, 0, 0, 0, 1, 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