Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35fbf381e53c6a3bdeaa1b7db5dd50615ce6e9578c3d21a94e68abf52bbf7361

Tx prefix hash: 797a43066db1417bf030e9f3d16386bbfa1c80c9424ffaac77c152da07fbed50
Tx public key: 4cb29927ab093bdd0c8efa8547a15b1f3627e8d46f003734b45f09ff87734bea
Timestamp: 1720981421 Timestamp [UCT]: 2024-07-14 18:23:41 Age [y:d:h:m:s]: 01:141:12:39:14
Block: 1065696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359695 RingCT/type: yes/0
Extra: 014cb29927ab093bdd0c8efa8547a15b1f3627e8d46f003734b45f09ff87734bea02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89170907a9525be400a2f54f03a91e21d228d57c5e472c7ac72fa1ea91f5d822 0.600000000000 1536245 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": 1065706, "vin": [ { "gen": { "height": 1065696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89170907a9525be400a2f54f03a91e21d228d57c5e472c7ac72fa1ea91f5d822" } } ], "extra": [ 1, 76, 178, 153, 39, 171, 9, 59, 221, 12, 142, 250, 133, 71, 161, 91, 31, 54, 39, 232, 212, 111, 0, 55, 52, 180, 95, 9, 255, 135, 115, 75, 234, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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