Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8726b00a7888017846c468358ec1f95214c5dd482c61e1d6155ad4e213a9d404

Tx prefix hash: dcefde93d71d69f194ee6d14b1a519fb7c16d1c8a210334b3c5c7234f366bd94
Tx public key: 486a52fcfb2ca261eb8c1c857f37b46b67c32e25074b2f3d87a72a10e1712e68
Timestamp: 1712742702 Timestamp [UCT]: 2024-04-10 09:51:42 Age [y:d:h:m:s]: 01:008:00:28:18
Block: 997369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266708 RingCT/type: yes/0
Extra: 01486a52fcfb2ca261eb8c1c857f37b46b67c32e25074b2f3d87a72a10e1712e68021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1fea7890286b7603abd060c0729f6c5dc17d3e68f305847c7b81f718cfd847d 0.600000000000 1457799 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": 997379, "vin": [ { "gen": { "height": 997369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1fea7890286b7603abd060c0729f6c5dc17d3e68f305847c7b81f718cfd847d" } } ], "extra": [ 1, 72, 106, 82, 252, 251, 44, 162, 97, 235, 140, 28, 133, 127, 55, 180, 107, 103, 195, 46, 37, 7, 75, 47, 61, 135, 167, 42, 16, 225, 113, 46, 104, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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