Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4db278a4a70ca7dcc4b2c47b14a1634167c640cd2187d90dc0113ef8a4bedd64

Tx prefix hash: f9d710254e300641ca4d56eff7dc3b90ad4c7e50b71dbf0ef1c7ed1b3f896b13
Tx public key: e9f0ac209f16fe84f9a1f7c1c2f07fea1fb96becb2baa1b63c6c483b4e99e613
Timestamp: 1669066702 Timestamp [UCT]: 2022-11-21 21:38:22 Age [y:d:h:m:s]: 02:141:11:05:15
Block: 636200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 622821 RingCT/type: yes/0
Extra: 01e9f0ac209f16fe84f9a1f7c1c2f07fea1fb96becb2baa1b63c6c483b4e99e61302110000000171bd5189000000000000000000

1 output(s) for total of 4.786359418000 dcy

stealth address amount amount idx
00: fec8c9fe840240939046de4546346e4209f92daffb1e4ba6daf290512023659f 4.786359418000 1075597 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": 636210, "vin": [ { "gen": { "height": 636200 } } ], "vout": [ { "amount": 4786359418, "target": { "key": "fec8c9fe840240939046de4546346e4209f92daffb1e4ba6daf290512023659f" } } ], "extra": [ 1, 233, 240, 172, 32, 159, 22, 254, 132, 249, 161, 247, 193, 194, 240, 127, 234, 31, 185, 107, 236, 178, 186, 161, 182, 60, 108, 72, 59, 78, 153, 230, 19, 2, 17, 0, 0, 0, 1, 113, 189, 81, 137, 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