Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d9b7901bd59f9e53f8da388937be6ce3c8de051f2c3a533618956cc202aa5f9

Tx prefix hash: d3051ab418d418a3ef2b7e2c0d800e78b04a055a106d8f940a69385286ca9ba5
Tx public key: adf387be716a0260b2df1fd13d4206e4590072627df6fbc89fa3d8cc1f8f140b
Timestamp: 1698513066 Timestamp [UCT]: 2023-10-28 17:11:06 Age [y:d:h:m:s]: 01:118:16:30:39
Block: 879632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345786 RingCT/type: yes/0
Extra: 01adf387be716a0260b2df1fd13d4206e4590072627df6fbc89fa3d8cc1f8f140b02110000000333af99f4000000000000000000

1 output(s) for total of 0.747160742000 dcy

stealth address amount amount idx
00: 294027037e657842e1488ab1b6fb7d2f04c76fab4d4bf162312bfa7ac4d6912a 0.747160742000 1335166 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": 879642, "vin": [ { "gen": { "height": 879632 } } ], "vout": [ { "amount": 747160742, "target": { "key": "294027037e657842e1488ab1b6fb7d2f04c76fab4d4bf162312bfa7ac4d6912a" } } ], "extra": [ 1, 173, 243, 135, 190, 113, 106, 2, 96, 178, 223, 31, 209, 61, 66, 6, 228, 89, 0, 114, 98, 125, 246, 251, 200, 159, 163, 216, 204, 31, 143, 20, 11, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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