Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a615ed5910786e83b90f7d8962aaefcfc7711f48f28217f351d8412ea70c2ebd

Tx prefix hash: d2048daf84458c05bc17905d80e53b6223c5876fe4a6c6d1940c9b9a5fe10460
Tx public key: 770e8d0a541096b4a6518c54246355075133d1a45dcea297d98b308e87bfa73b
Timestamp: 1574667612 Timestamp [UCT]: 2019-11-25 07:40:12 Age [y:d:h:m:s]: 05:039:12:15:39
Block: 17014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1171076 RingCT/type: yes/0
Extra: 01770e8d0a541096b4a6518c54246355075133d1a45dcea297d98b308e87bfa73b021100000001f95225a5000000000000000000

1 output(s) for total of 539.154075468000 dcy

stealth address amount amount idx
00: 3090d28d023eb0f1862df4ff4e8ef0c7782d7785023d2f6a1ba16794f10193b8 539.154075468000 24284 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": 17024, "vin": [ { "gen": { "height": 17014 } } ], "vout": [ { "amount": 539154075468, "target": { "key": "3090d28d023eb0f1862df4ff4e8ef0c7782d7785023d2f6a1ba16794f10193b8" } } ], "extra": [ 1, 119, 14, 141, 10, 84, 16, 150, 180, 166, 81, 140, 84, 36, 99, 85, 7, 81, 51, 209, 164, 93, 206, 162, 151, 217, 139, 48, 142, 135, 191, 167, 59, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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