Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 589f6f1f7233296459ff57ed12ee7693e186fd2f5a90f37cc98533e7b317940d

Tx prefix hash: 6cebec1b183ad3ffed951a2c4fd5412905a57abc25e9de72f2ec23b121d6c55a
Tx public key: ffdb24f1721aacb4ba01dec8a0a51c75bfc93f89bb238224fd9dc4254acfe1d6
Timestamp: 1723222682 Timestamp [UCT]: 2024-08-09 16:58:02 Age [y:d:h:m:s]: 00:154:03:07:04
Block: 1084280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110254 RingCT/type: yes/0
Extra: 01ffdb24f1721aacb4ba01dec8a0a51c75bfc93f89bb238224fd9dc4254acfe1d6021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9693c013304795bf43628718e9bd40ea4db7bf22d22aa87f9a16929db35eef74 0.600000000000 1558497 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": 1084290, "vin": [ { "gen": { "height": 1084280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9693c013304795bf43628718e9bd40ea4db7bf22d22aa87f9a16929db35eef74" } } ], "extra": [ 1, 255, 219, 36, 241, 114, 26, 172, 180, 186, 1, 222, 200, 160, 165, 28, 117, 191, 201, 63, 137, 187, 35, 130, 36, 253, 157, 196, 37, 74, 207, 225, 214, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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