Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6225c711496d8b46b8aaebf1ca4664c42241b0161cc363fd3dc6148b9e44e2d

Tx prefix hash: 42e294fb9cfefbcca11c4be1c0928f363ac8065198fe928b25c8ce3d1e7ad864
Tx public key: 884069a0533b55671d199e16cf2b124571cb462deaf7e74ec0241f2cca6ff095
Timestamp: 1631639382 Timestamp [UCT]: 2021-09-14 17:09:42 Age [y:d:h:m:s]: 04:047:15:01:22
Block: 333754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1068049 RingCT/type: yes/0
Extra: 01884069a0533b55671d199e16cf2b124571cb462deaf7e74ec0241f2cca6ff095021100000001f29d7abf000000000000000000

1 output(s) for total of 48.098871957000 dcy

stealth address amount amount idx
00: f24f9c3adeec71f2ac3257a6cbd8bc0f81ec9d4be1a615ba5f959d1c7024a70a 48.098871957000 688597 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": 333764, "vin": [ { "gen": { "height": 333754 } } ], "vout": [ { "amount": 48098871957, "target": { "key": "f24f9c3adeec71f2ac3257a6cbd8bc0f81ec9d4be1a615ba5f959d1c7024a70a" } } ], "extra": [ 1, 136, 64, 105, 160, 83, 59, 85, 103, 29, 25, 158, 22, 207, 43, 18, 69, 113, 203, 70, 45, 234, 247, 231, 78, 192, 36, 31, 44, 202, 111, 240, 149, 2, 17, 0, 0, 0, 1, 242, 157, 122, 191, 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