Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d2e9105b29a9063c30ae1f1e2a2fea64bbd76fc5baabe37ce392d68c5e980b8

Tx prefix hash: c908d38a0ae51b7d2bfd4b92c5d5ab9bbd6c263d6c4c709def491331bbf9b540
Tx public key: 4678c1fe9cb03ad999bcb95dc655576ccbc84180edc9de6e0e20135df97a77f8
Timestamp: 1726913211 Timestamp [UCT]: 2024-09-21 10:06:51 Age [y:d:h:m:s]: 00:194:11:51:58
Block: 1114870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138807 RingCT/type: yes/0
Extra: 014678c1fe9cb03ad999bcb95dc655576ccbc84180edc9de6e0e20135df97a77f8021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 876980ae730ae2dfb4feaa8f26fd1bdf80c55f0a94cfe9f747403a070c754b8f 0.600000000000 1594801 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": 1114880, "vin": [ { "gen": { "height": 1114870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "876980ae730ae2dfb4feaa8f26fd1bdf80c55f0a94cfe9f747403a070c754b8f" } } ], "extra": [ 1, 70, 120, 193, 254, 156, 176, 58, 217, 153, 188, 185, 93, 198, 85, 87, 108, 203, 200, 65, 128, 237, 201, 222, 110, 14, 32, 19, 93, 249, 122, 119, 248, 2, 17, 0, 0, 0, 1, 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