Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90e74213bd3aaf860eabca8b8182296f916b7fc9e85f90bbffa1718c85401864

Tx prefix hash: fbac9173659ebfcf1c34ecd6f8a3f928416d9ab29012c07c35a73ef6b3915d16
Tx public key: b7fac93f32bd88dad88744f1707c7cc0132c1ee3440572ad7b1b58e9b45ab4f4
Timestamp: 1578007009 Timestamp [UCT]: 2020-01-02 23:16:49 Age [y:d:h:m:s]: 05:062:06:57:56
Block: 37468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194288 RingCT/type: yes/0
Extra: 01b7fac93f32bd88dad88744f1707c7cc0132c1ee3440572ad7b1b58e9b45ab4f402110000000cd81c26c0000000000000000000

1 output(s) for total of 461.162318179000 dcy

stealth address amount amount idx
00: 8bf3b22e1e3107958feab51ebac6552a0f08a2a3e25a7e24214670dc7165d562 461.162318179000 63622 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": 37478, "vin": [ { "gen": { "height": 37468 } } ], "vout": [ { "amount": 461162318179, "target": { "key": "8bf3b22e1e3107958feab51ebac6552a0f08a2a3e25a7e24214670dc7165d562" } } ], "extra": [ 1, 183, 250, 201, 63, 50, 189, 136, 218, 216, 135, 68, 241, 112, 124, 124, 192, 19, 44, 30, 227, 68, 5, 114, 173, 123, 27, 88, 233, 180, 90, 180, 244, 2, 17, 0, 0, 0, 12, 216, 28, 38, 192, 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