Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1d550f93d4e534e168e968902bf65b86422be8290c7dfa5d6ef925cf5c978da

Tx prefix hash: 1e50431869371c86c55129c95ad0c4bf9f9dc44b6f01a61416667b4ccc5ddca4
Tx public key: c00dbdb17a033799622468be793d6e75cecc9a815ccee58b077f073c1e6609a5
Timestamp: 1580263407 Timestamp [UCT]: 2020-01-29 02:03:27 Age [y:d:h:m:s]: 05:012:19:06:17
Block: 54284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1160764 RingCT/type: yes/0
Extra: 01c00dbdb17a033799622468be793d6e75cecc9a815ccee58b077f073c1e6609a5021100000002dcee4b4d000000000000000000

1 output(s) for total of 405.634980886000 dcy

stealth address amount amount idx
00: f369b039317bade5637b57b6b26faa213fb98ffe8454ed5674a30505b0c30b75 405.634980886000 100625 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": 54294, "vin": [ { "gen": { "height": 54284 } } ], "vout": [ { "amount": 405634980886, "target": { "key": "f369b039317bade5637b57b6b26faa213fb98ffe8454ed5674a30505b0c30b75" } } ], "extra": [ 1, 192, 13, 189, 177, 122, 3, 55, 153, 98, 36, 104, 190, 121, 61, 110, 117, 206, 204, 154, 129, 92, 206, 229, 139, 7, 127, 7, 60, 30, 102, 9, 165, 2, 17, 0, 0, 0, 2, 220, 238, 75, 77, 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