Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ed8829c96b9693175279d668cef4c20e5a549408fc5bbe0339bf91a29947cc9

Tx prefix hash: 48e3222619d73c413a3bd82a802c10898a9e214defe7e5d94505dc5d62f74a8d
Tx public key: 7d0a547faffdb7fdd21bbfa448fdb251a9ab29ad66c7f09f6efa4f304f71e768
Timestamp: 1700993423 Timestamp [UCT]: 2023-11-26 10:10:23 Age [y:d:h:m:s]: 01:357:12:12:25
Block: 899977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514407 RingCT/type: yes/0
Extra: 017d0a547faffdb7fdd21bbfa448fdb251a9ab29ad66c7f09f6efa4f304f71e76802110000000de6d27f9c000000000000000000

1 output(s) for total of 0.639738642000 dcy

stealth address amount amount idx
00: 1dab8edcefff1bc75fe19a1573c923be98c6fc5be983781cec42f5c2e0e19027 0.639738642000 1356448 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": 899987, "vin": [ { "gen": { "height": 899977 } } ], "vout": [ { "amount": 639738642, "target": { "key": "1dab8edcefff1bc75fe19a1573c923be98c6fc5be983781cec42f5c2e0e19027" } } ], "extra": [ 1, 125, 10, 84, 127, 175, 253, 183, 253, 210, 27, 191, 164, 72, 253, 178, 81, 169, 171, 41, 173, 102, 199, 240, 159, 110, 250, 79, 48, 79, 113, 231, 104, 2, 17, 0, 0, 0, 13, 230, 210, 127, 156, 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