Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85e90961b4360652a27f014aa2c759ccebc2c8317463b0ac5b32742410af6a2b

Tx prefix hash: 725065ca0e9b82d39b4aa556f99b2361e84c37324679d3a4e6ec20a853663859
Tx public key: e50db79b3d8776e2f9bd41c6bc201360a09251f4221b0fcc49dce8abd3e5e09d
Timestamp: 1730556069 Timestamp [UCT]: 2024-11-02 14:01:09 Age [y:d:h:m:s]: 00:083:00:35:12
Block: 1144985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59360 RingCT/type: yes/0
Extra: 01e50db79b3d8776e2f9bd41c6bc201360a09251f4221b0fcc49dce8abd3e5e09d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99eb491d302b4f7943955a7d535704270b342319ae94a3972ee19e44d153d363 0.600000000000 1629340 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": 1144995, "vin": [ { "gen": { "height": 1144985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99eb491d302b4f7943955a7d535704270b342319ae94a3972ee19e44d153d363" } } ], "extra": [ 1, 229, 13, 183, 155, 61, 135, 118, 226, 249, 189, 65, 198, 188, 32, 19, 96, 160, 146, 81, 244, 34, 27, 15, 204, 73, 220, 232, 171, 211, 229, 224, 157, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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