Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1251c473a5beb6ae583d45ebc47fe80ded7856d27889a37c59fdb872483b701d

Tx prefix hash: 82a4f05de4f0537f60a5adfa10cd6876385cadfd56538da24dc05bd50ffbcf00
Tx public key: 296d47bfb6c3c035f4a4dc32ffbb85ec4c38a1604dc83b185fabfcd3cdf442cb
Timestamp: 1719752316 Timestamp [UCT]: 2024-06-30 12:58:36 Age [y:d:h:m:s]: 00:349:22:44:26
Block: 1055498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250009 RingCT/type: yes/0
Extra: 01296d47bfb6c3c035f4a4dc32ffbb85ec4c38a1604dc83b185fabfcd3cdf442cb02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6eab7135b64a111c02b920e7d6fa31c8cd1f0e7106e04d7a902176b9254d0d72 0.600000000000 1525903 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": 1055508, "vin": [ { "gen": { "height": 1055498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6eab7135b64a111c02b920e7d6fa31c8cd1f0e7106e04d7a902176b9254d0d72" } } ], "extra": [ 1, 41, 109, 71, 191, 182, 195, 192, 53, 244, 164, 220, 50, 255, 187, 133, 236, 76, 56, 161, 96, 77, 200, 59, 24, 95, 171, 252, 211, 205, 244, 66, 203, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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