Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8782be46b933cf4d6d523c7b03c474cc93c732fa76b62e67033d2404ff72944f

Tx prefix hash: 6795251d5e18c60aaa39a0dc44e1e0035984f475033430ad27dfe5bc625346d5
Tx public key: 7f842e2fed403bd7d11fc49cbd919f6f90eee31936616b54a1b46698c1c3a98d
Timestamp: 1587789760 Timestamp [UCT]: 2020-04-25 04:42:40 Age [y:d:h:m:s]: 04:252:04:27:40
Block: 96086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1091687 RingCT/type: yes/0
Extra: 017f842e2fed403bd7d11fc49cbd919f6f90eee31936616b54a1b46698c1c3a98d0211000000098a2ee0d9000000000000000000

1 output(s) for total of 294.873305444000 dcy

stealth address amount amount idx
00: bc4d0403b9a35a06b50360c809b2addc99582533b5ce80fe6d0f0fa3dfd4b9c1 294.873305444000 170501 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": 96096, "vin": [ { "gen": { "height": 96086 } } ], "vout": [ { "amount": 294873305444, "target": { "key": "bc4d0403b9a35a06b50360c809b2addc99582533b5ce80fe6d0f0fa3dfd4b9c1" } } ], "extra": [ 1, 127, 132, 46, 47, 237, 64, 59, 215, 209, 31, 196, 156, 189, 145, 159, 111, 144, 238, 227, 25, 54, 97, 107, 84, 161, 180, 102, 152, 193, 195, 169, 141, 2, 17, 0, 0, 0, 9, 138, 46, 224, 217, 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