Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43a25eab1bd39c883a058617c8bbdeca9c41efe58aace96d33e70c24446a1046

Tx prefix hash: 271c8d4b63356cfc478d79c46c2f9341050c95c2bf6f3dccd0f0d895a9653ac0
Tx public key: efd7d1be6b660cf85f42904a01d214df1df496e94842bc4db183926023bd14a9
Timestamp: 1723039260 Timestamp [UCT]: 2024-08-07 14:01:00 Age [y:d:h:m:s]: 00:232:19:29:07
Block: 1082750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166274 RingCT/type: yes/0
Extra: 01efd7d1be6b660cf85f42904a01d214df1df496e94842bc4db183926023bd14a902110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f1338a43d02c9a2f8e3e0bf01cc9db103f9b0e69433b6101e9e24408230c82d 0.600000000000 1556581 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": 1082760, "vin": [ { "gen": { "height": 1082750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f1338a43d02c9a2f8e3e0bf01cc9db103f9b0e69433b6101e9e24408230c82d" } } ], "extra": [ 1, 239, 215, 209, 190, 107, 102, 12, 248, 95, 66, 144, 74, 1, 210, 20, 223, 29, 244, 150, 233, 72, 66, 188, 77, 177, 131, 146, 96, 35, 189, 20, 169, 2, 17, 0, 0, 0, 9, 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