Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1db315985c075f0ad63a3b446fb45a9d1d64dfe112d2002af709f557ae08e49

Tx prefix hash: 4b83effb860d1a47b9f8cbf972fcda3004620ab03078a12d92b41d18b60698a3
Tx public key: 7773e7e7a0fbfa6a143f16e333a48cfa2991a9bedf89efa222a0e12441e74e50
Timestamp: 1714134486 Timestamp [UCT]: 2024-04-26 12:28:06 Age [y:d:h:m:s]: 00:304:17:29:15
Block: 1008927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217808 RingCT/type: yes/0
Extra: 017773e7e7a0fbfa6a143f16e333a48cfa2991a9bedf89efa222a0e12441e74e5002110000000118ec9060000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7eb82c55c918e12e61a9c34221b0a9e6da796f650d4bfe81019d8c15e6723a19 0.600000000000 1470443 of 15

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": 1008937, "vin": [ { "gen": { "height": 1008927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7eb82c55c918e12e61a9c34221b0a9e6da796f650d4bfe81019d8c15e6723a19" } } ], "extra": [ 1, 119, 115, 231, 231, 160, 251, 250, 106, 20, 63, 22, 227, 51, 164, 140, 250, 41, 145, 169, 190, 223, 137, 239, 162, 34, 160, 225, 36, 65, 231, 78, 80, 2, 17, 0, 0, 0, 1, 24, 236, 144, 96, 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