Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6d3f8a78f163378de4e7cd08378d4bc8ba43eb98ae9abf3b846c642a4d32d36

Tx prefix hash: 5c9dfa4e6e3a47a8669c0107ba43c72007bd79314babdac1dbf8bab3904ca071
Tx public key: 6e79616942d1485e3bfd943943a3d93a9589938bfc4909357dae94780b889a36
Timestamp: 1578181107 Timestamp [UCT]: 2020-01-04 23:38:27 Age [y:d:h:m:s]: 05:037:05:39:12
Block: 38854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176436 RingCT/type: yes/0
Extra: 016e79616942d1485e3bfd943943a3d93a9589938bfc4909357dae94780b889a360211000000084ac5aa02000000000000000000

1 output(s) for total of 456.311504428000 dcy

stealth address amount amount idx
00: e6f1f5386a968a7cc66c699cfc422f7d583543e8f1373d832feb4930849130b2 456.311504428000 66551 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": 38864, "vin": [ { "gen": { "height": 38854 } } ], "vout": [ { "amount": 456311504428, "target": { "key": "e6f1f5386a968a7cc66c699cfc422f7d583543e8f1373d832feb4930849130b2" } } ], "extra": [ 1, 110, 121, 97, 105, 66, 209, 72, 94, 59, 253, 148, 57, 67, 163, 217, 58, 149, 137, 147, 139, 252, 73, 9, 53, 125, 174, 148, 120, 11, 136, 154, 54, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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