Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 199cd51363fcd5d62a2c6c122b72415491b09f2b74663e673367b110b8c7dbcf

Tx prefix hash: b823d361850844887f9fe007c64f5f03c86b8b90562010a355c8fc138c6d7885
Tx public key: 61ca35a31c7b46ec86c9c3bd33592b65d3a7665ba4886fe8a5e70b76998b636f
Timestamp: 1696163670 Timestamp [UCT]: 2023-10-01 12:34:30 Age [y:d:h:m:s]: 01:103:05:11:45
Block: 860141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335037 RingCT/type: yes/0
Extra: 0161ca35a31c7b46ec86c9c3bd33592b65d3a7665ba4886fe8a5e70b76998b636f0211000000014b8f5122000000000000000000

1 output(s) for total of 0.866953586000 dcy

stealth address amount amount idx
00: c97397589005e1f91c19ce6b6fb4b031bebb85e77e1a6c19f1ed14cdf53b18a4 0.866953586000 1314409 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": 860151, "vin": [ { "gen": { "height": 860141 } } ], "vout": [ { "amount": 866953586, "target": { "key": "c97397589005e1f91c19ce6b6fb4b031bebb85e77e1a6c19f1ed14cdf53b18a4" } } ], "extra": [ 1, 97, 202, 53, 163, 28, 123, 70, 236, 134, 201, 195, 189, 51, 89, 43, 101, 211, 167, 102, 91, 164, 136, 111, 232, 165, 231, 11, 118, 153, 139, 99, 111, 2, 17, 0, 0, 0, 1, 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