Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1745b66b28cf4254f449543c88c2daab375c87b7fb7bb58da0cfef62c883bca

Tx prefix hash: ddbbf83ef031bfd1ab034c90c35fe44496545accbc762a7f9542468cdfd3882c
Tx public key: 2201a0e433a0523ae61221558ca9e5959c4742e97112bc154aafd733dfa1f49a
Timestamp: 1581320954 Timestamp [UCT]: 2020-02-10 07:49:14 Age [y:d:h:m:s]: 04:281:07:03:28
Block: 61789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093243 RingCT/type: yes/0
Extra: 012201a0e433a0523ae61221558ca9e5959c4742e97112bc154aafd733dfa1f49a02110000000bd81c26c0000000000000000000

1 output(s) for total of 383.061238852000 dcy

stealth address amount amount idx
00: e2b9f75d529b8126a72dc44896e89569292c2f2044e8e712a9cb3b972c708e7f 383.061238852000 113952 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": 61799, "vin": [ { "gen": { "height": 61789 } } ], "vout": [ { "amount": 383061238852, "target": { "key": "e2b9f75d529b8126a72dc44896e89569292c2f2044e8e712a9cb3b972c708e7f" } } ], "extra": [ 1, 34, 1, 160, 228, 51, 160, 82, 58, 230, 18, 33, 85, 140, 169, 229, 149, 156, 71, 66, 233, 113, 18, 188, 21, 74, 175, 215, 51, 223, 161, 244, 154, 2, 17, 0, 0, 0, 11, 216, 28, 38, 192, 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