Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89ae06c652838f1be7a4eb9e0c283f010bec3ec403592ecde2bbb89871780c3e

Tx prefix hash: 908997be143586410ee05249f751f5a6e141336eae23e88f6a82537589097ee4
Tx public key: 652cbce09195f7cc229a1728ccf5ab2329db85e5a9f5d31a4b527916c14496ca
Timestamp: 1674861485 Timestamp [UCT]: 2023-01-27 23:18:05 Age [y:d:h:m:s]: 02:124:13:08:34
Block: 684220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 610694 RingCT/type: yes/0
Extra: 01652cbce09195f7cc229a1728ccf5ab2329db85e5a9f5d31a4b527916c14496ca0211000000015029cbac000000000000000000

1 output(s) for total of 3.318142576000 dcy

stealth address amount amount idx
00: af52d70954043649ee3de7e1d9b5c9fa6a69d5b792bffd3c3c0ce7d4c8ccedf7 3.318142576000 1126435 of 0

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": 684230, "vin": [ { "gen": { "height": 684220 } } ], "vout": [ { "amount": 3318142576, "target": { "key": "af52d70954043649ee3de7e1d9b5c9fa6a69d5b792bffd3c3c0ce7d4c8ccedf7" } } ], "extra": [ 1, 101, 44, 188, 224, 145, 149, 247, 204, 34, 154, 23, 40, 204, 245, 171, 35, 41, 219, 133, 229, 169, 245, 211, 26, 75, 82, 121, 22, 193, 68, 150, 202, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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