Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 069e245cc17522fbb246e6ecdd5954749a81fc70da82cfde0da104f75b9afb1e

Tx prefix hash: fc2816fc9a68d193d9ed17c01234d2f61fdb2ede886020fa6cc5cbc9d1f03250
Tx public key: 55c7b66e8d3d7a26e9c493b4c76c56593c7288ed944af0d17123e7c80214f2a2
Timestamp: 1693607149 Timestamp [UCT]: 2023-09-01 22:25:49 Age [y:d:h:m:s]: 01:214:05:02:35
Block: 838924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414205 RingCT/type: yes/0
Extra: 0155c7b66e8d3d7a26e9c493b4c76c56593c7288ed944af0d17123e7c80214f2a202110000001b4b8f5122000000000000000000

1 output(s) for total of 1.019287286000 dcy

stealth address amount amount idx
00: bb0543a3e2df1a4dc13a1551ca302a90b5bdebc05bde56b964b270b9fbd04941 1.019287286000 1291722 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": 838934, "vin": [ { "gen": { "height": 838924 } } ], "vout": [ { "amount": 1019287286, "target": { "key": "bb0543a3e2df1a4dc13a1551ca302a90b5bdebc05bde56b964b270b9fbd04941" } } ], "extra": [ 1, 85, 199, 182, 110, 141, 61, 122, 38, 233, 196, 147, 180, 199, 108, 86, 89, 60, 114, 136, 237, 148, 74, 240, 209, 113, 35, 231, 200, 2, 20, 242, 162, 2, 17, 0, 0, 0, 27, 75, 143, 81, 34, 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