Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a0524d1c5b1f764b741213ffd4604529fd3f78d10b080bc4467b9ff639e1413

Tx prefix hash: 6070a95cad687b9f5b06a8ddb2bf02a70d470ac5683fa55c5084be94b9ca670d
Tx public key: 0a52279c444f5c699fb9f927caa104fb601202326954e918a590f3f8c884a5d1
Timestamp: 1723567962 Timestamp [UCT]: 2024-08-13 16:52:42 Age [y:d:h:m:s]: 01:111:05:23:49
Block: 1087142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337990 RingCT/type: yes/0
Extra: 010a52279c444f5c699fb9f927caa104fb601202326954e918a590f3f8c884a5d1021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c90b7fe375056c2b4f97927c2a66c11f30e06eb1a95f18096a2228ba5bb78f93 0.600000000000 1561747 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": 1087152, "vin": [ { "gen": { "height": 1087142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c90b7fe375056c2b4f97927c2a66c11f30e06eb1a95f18096a2228ba5bb78f93" } } ], "extra": [ 1, 10, 82, 39, 156, 68, 79, 92, 105, 159, 185, 249, 39, 202, 161, 4, 251, 96, 18, 2, 50, 105, 84, 233, 24, 165, 144, 243, 248, 200, 132, 165, 209, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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