Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0047110322cee10a28c483012acfd11af62426ff44042df9ee85f2e7e5b9ac98

Tx prefix hash: 689efedf9a835d24462624f82f40e51a4e3dba60b8b67e6b9f0749d2e06ef73c
Tx public key: a02b2f4434678e77ff36bd4f502328cb24a59c65cb295a84d71884967b9f2a13
Timestamp: 1633179141 Timestamp [UCT]: 2021-10-02 12:52:21 Age [y:d:h:m:s]: 04:030:09:05:11
Block: 345185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1057020 RingCT/type: yes/0
Extra: 01a02b2f4434678e77ff36bd4f502328cb24a59c65cb295a84d71884967b9f2a13021100000001f60c5d7e000000000000000000

1 output(s) for total of 44.081790782000 dcy

stealth address amount amount idx
00: 10978203387f8d0a1a342585e59b537936fa08a185598f1320b3130384923957 44.081790782000 708107 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": 345195, "vin": [ { "gen": { "height": 345185 } } ], "vout": [ { "amount": 44081790782, "target": { "key": "10978203387f8d0a1a342585e59b537936fa08a185598f1320b3130384923957" } } ], "extra": [ 1, 160, 43, 47, 68, 52, 103, 142, 119, 255, 54, 189, 79, 80, 35, 40, 203, 36, 165, 156, 101, 203, 41, 90, 132, 215, 24, 132, 150, 123, 159, 42, 19, 2, 17, 0, 0, 0, 1, 246, 12, 93, 126, 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