Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70e1c6d57af56bff0b995a281504bd735ef85ec8f7a3ca4839bf1549ab96673b

Tx prefix hash: d3fcba7f76c5b50f3b4f936c3ab0f749227631903ca4a93ac83f57155c1af3ba
Tx public key: d1f926536a8c78ef9fc2f25ae6ab60e8e9bafe274eba42c1b084131dec6a4cc4
Timestamp: 1582381697 Timestamp [UCT]: 2020-02-22 14:28:17 Age [y:d:h:m:s]: 05:055:13:42:07
Block: 70211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1192957 RingCT/type: yes/0
Extra: 01d1f926536a8c78ef9fc2f25ae6ab60e8e9bafe274eba42c1b084131dec6a4cc4021100000001c71d3ff9000000000000000000

1 output(s) for total of 359.221741841000 dcy

stealth address amount amount idx
00: e36e4968f4d4fad733e85206f833b2242b0c3cfb42412c2bce5a335ec552f788 359.221741841000 129662 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": 70221, "vin": [ { "gen": { "height": 70211 } } ], "vout": [ { "amount": 359221741841, "target": { "key": "e36e4968f4d4fad733e85206f833b2242b0c3cfb42412c2bce5a335ec552f788" } } ], "extra": [ 1, 209, 249, 38, 83, 106, 140, 120, 239, 159, 194, 242, 90, 230, 171, 96, 232, 233, 186, 254, 39, 78, 186, 66, 193, 176, 132, 19, 29, 236, 106, 76, 196, 2, 17, 0, 0, 0, 1, 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