Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08d66101b25ad1c7ebf7cd61456799a258d0e0496f64b161e22a7b21ce417520

Tx prefix hash: c43f1cc576e97d40ff9c06d3efb1f0ec2b63300e466c64dc39f901169a3c5f24
Tx public key: eb025613aa5b036316240a1ededf0ff080276c482c8b0d49bf6a6ded5b1f61f2
Timestamp: 1583855967 Timestamp [UCT]: 2020-03-10 15:59:27 Age [y:d:h:m:s]: 04:250:21:23:57
Block: 79920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074346 RingCT/type: yes/0
Extra: 01eb025613aa5b036316240a1ededf0ff080276c482c8b0d49bf6a6ded5b1f61f202110000000428db8c57000000000000000000

1 output(s) for total of 333.574354039000 dcy

stealth address amount amount idx
00: e9f7d646c18fb1efab95fca7f02a970ab4343c14bfd76daea87f89a944d4190d 333.574354039000 146228 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": 79930, "vin": [ { "gen": { "height": 79920 } } ], "vout": [ { "amount": 333574354039, "target": { "key": "e9f7d646c18fb1efab95fca7f02a970ab4343c14bfd76daea87f89a944d4190d" } } ], "extra": [ 1, 235, 2, 86, 19, 170, 91, 3, 99, 22, 36, 10, 30, 222, 223, 15, 240, 128, 39, 108, 72, 44, 139, 13, 73, 191, 106, 109, 237, 91, 31, 97, 242, 2, 17, 0, 0, 0, 4, 40, 219, 140, 87, 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