Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 019c013519210bfef30409f81a4ab130b518bc1eb6226ef46fcf2e6e98666f3f

Tx prefix hash: d8d79ef8c18b4f4ea93d1806aa2c4d84adfe59a4c806cad72bdd5324e92d6d15
Tx public key: c179304aa19831768e5058d1a52a9afc0fb321355cf21d8b7c52dab70150e86b
Timestamp: 1585549180 Timestamp [UCT]: 2020-03-30 06:19:40 Age [y:d:h:m:s]: 04:276:16:49:07
Block: 89575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1097180 RingCT/type: yes/0
Extra: 01c179304aa19831768e5058d1a52a9afc0fb321355cf21d8b7c52dab70150e86b02110000000a60e3cc90000000000000000000

1 output(s) for total of 309.885757681000 dcy

stealth address amount amount idx
00: 6a929f7ddf8d4b83300d3dac23b93cc6a755aaef740f6aaa117f0a21a8c95e87 309.885757681000 160703 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": 89585, "vin": [ { "gen": { "height": 89575 } } ], "vout": [ { "amount": 309885757681, "target": { "key": "6a929f7ddf8d4b83300d3dac23b93cc6a755aaef740f6aaa117f0a21a8c95e87" } } ], "extra": [ 1, 193, 121, 48, 74, 161, 152, 49, 118, 142, 80, 88, 209, 165, 42, 154, 252, 15, 179, 33, 53, 92, 242, 29, 139, 124, 82, 218, 183, 1, 80, 232, 107, 2, 17, 0, 0, 0, 10, 96, 227, 204, 144, 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