Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb3de0a650a14b2efbf7f13ba9829e5fd12465e9230a3a039fd5d8ac7c551890

Tx prefix hash: e7e9eb793ac6b9fd8fffe51d48af3daf6a70491c92c80e3b696e53b9053e62c1
Tx public key: 11f89dd20fb544330bbda5e655523c2a532a4b37a220212728529bbded96bf6b
Timestamp: 1584924244 Timestamp [UCT]: 2020-03-23 00:44:04 Age [y:d:h:m:s]: 05:033:01:27:17
Block: 87052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181068 RingCT/type: yes/0
Extra: 0111f89dd20fb544330bbda5e655523c2a532a4b37a220212728529bbded96bf6b02110000007a168ad909000000000000000000

1 output(s) for total of 315.908540147000 dcy

stealth address amount amount idx
00: 0f6a4b0e099f7ace5ed9fe570d40fd533880760e790ab202ceb16de2aca507db 315.908540147000 156950 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": 87062, "vin": [ { "gen": { "height": 87052 } } ], "vout": [ { "amount": 315908540147, "target": { "key": "0f6a4b0e099f7ace5ed9fe570d40fd533880760e790ab202ceb16de2aca507db" } } ], "extra": [ 1, 17, 248, 157, 210, 15, 181, 68, 51, 11, 189, 165, 230, 85, 82, 60, 42, 83, 42, 75, 55, 162, 32, 33, 39, 40, 82, 155, 189, 237, 150, 191, 107, 2, 17, 0, 0, 0, 122, 22, 138, 217, 9, 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