Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c87f8d35374e8b83c7565f68c3fabe8ea9f2c704cbc598668470a0bb71cf05a9

Tx prefix hash: d7f821c9a2d147960ce12bed5a0846e6e461152745828fd85755f15a52bee97e
Tx public key: b8696dfe55bcfd1614775f13b5aa0dbaa214e8f1ff4511cc88b287418bcf877b
Timestamp: 1657024303 Timestamp [UCT]: 2022-07-05 12:31:43 Age [y:d:h:m:s]: 02:292:08:18:21
Block: 537169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 730078 RingCT/type: yes/0
Extra: 01b8696dfe55bcfd1614775f13b5aa0dbaa214e8f1ff4511cc88b287418bcf877b0211000000014da16a3a000000000000000000

1 output(s) for total of 10.189110323000 dcy

stealth address amount amount idx
00: 8aa1460ebafdbe7b171a115bc6c192dfa0eff6b3c6a4a2be15548acd4e8455ac 10.189110323000 967028 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": 537179, "vin": [ { "gen": { "height": 537169 } } ], "vout": [ { "amount": 10189110323, "target": { "key": "8aa1460ebafdbe7b171a115bc6c192dfa0eff6b3c6a4a2be15548acd4e8455ac" } } ], "extra": [ 1, 184, 105, 109, 254, 85, 188, 253, 22, 20, 119, 95, 19, 181, 170, 13, 186, 162, 20, 232, 241, 255, 69, 17, 204, 136, 178, 135, 65, 139, 207, 135, 123, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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