Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02c5820335a64e50e16474131460d174df4b4a065af296ee922383920aba290e

Tx prefix hash: b7ffd6c8b64a6c7451caf2f546fd7b7dbdf4232d4d0cf3b85be3d1c51045ea32
Tx public key: 398f53cd6f4cab08a1f28d874c5338b9a9b88dd418fd1624f9dfae66f9bb9251
Timestamp: 1708003904 Timestamp [UCT]: 2024-02-15 13:31:44 Age [y:d:h:m:s]: 01:040:01:29:53
Block: 958096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289645 RingCT/type: yes/0
Extra: 01398f53cd6f4cab08a1f28d874c5338b9a9b88dd418fd1624f9dfae66f9bb925102110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d1ab57305ffd1f9b432abbd7616361f2bc1e10e23c818f2d939a136fec7ed13 0.600000000000 1417449 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": 958106, "vin": [ { "gen": { "height": 958096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d1ab57305ffd1f9b432abbd7616361f2bc1e10e23c818f2d939a136fec7ed13" } } ], "extra": [ 1, 57, 143, 83, 205, 111, 76, 171, 8, 161, 242, 141, 135, 76, 83, 56, 185, 169, 184, 141, 212, 24, 253, 22, 36, 249, 223, 174, 102, 249, 187, 146, 81, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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