Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4b95c40bfc77177bde93e703bd5f3e831c64880ebba5ce9d1d4fe1f21bbea46

Tx prefix hash: d742ae2a5aba2143848ff0f93aafcf5791b5f0ad95372e8434d97f5ff9caf8ab
Tx public key: e977c05da1ebd8552fadd5a6b053ab2809735a38525311d06cc7882611ed4cac
Timestamp: 1581474337 Timestamp [UCT]: 2020-02-12 02:25:37 Age [y:d:h:m:s]: 04:323:18:00:38
Block: 63138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123537 RingCT/type: yes/0
Extra: 01e977c05da1ebd8552fadd5a6b053ab2809735a38525311d06cc7882611ed4cac021100000010c71d3ff9000000000000000000

1 output(s) for total of 379.145496026000 dcy

stealth address amount amount idx
00: 2637e2f8def6789255f0dfd2edce851bff895284413b5bd8ceee1f5e1e8ab502 379.145496026000 116426 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": 63148, "vin": [ { "gen": { "height": 63138 } } ], "vout": [ { "amount": 379145496026, "target": { "key": "2637e2f8def6789255f0dfd2edce851bff895284413b5bd8ceee1f5e1e8ab502" } } ], "extra": [ 1, 233, 119, 192, 93, 161, 235, 216, 85, 47, 173, 213, 166, 176, 83, 171, 40, 9, 115, 90, 56, 82, 83, 17, 208, 108, 199, 136, 38, 17, 237, 76, 172, 2, 17, 0, 0, 0, 16, 199, 29, 63, 249, 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