Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7979c986681f60c57b733417e0f18dab95892b2dcb6066909c396d8fe22b8d8f

Tx prefix hash: 4b1458997446549b9867e4fc6f1ccb72dc71a27b04f92977aa66577717c6c315
Tx public key: ac372c92721541c78e8e85b92a6ed53127a56f069863bc878cc6f9aced5bf3a3
Timestamp: 1708633339 Timestamp [UCT]: 2024-02-22 20:22:19 Age [y:d:h:m:s]: 01:044:22:35:35
Block: 963316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293137 RingCT/type: yes/0
Extra: 01ac372c92721541c78e8e85b92a6ed53127a56f069863bc878cc6f9aced5bf3a302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acbbf5b0f4431c68a8b71bd19c255d3a11aae211ada29cfd730f5e268d52c0fd 0.600000000000 1423017 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": 963326, "vin": [ { "gen": { "height": 963316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acbbf5b0f4431c68a8b71bd19c255d3a11aae211ada29cfd730f5e268d52c0fd" } } ], "extra": [ 1, 172, 55, 44, 146, 114, 21, 65, 199, 142, 142, 133, 185, 42, 110, 213, 49, 39, 165, 111, 6, 152, 99, 188, 135, 140, 198, 249, 172, 237, 91, 243, 163, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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