Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 315e52be9011d6589095d6f3d33e9d10a88d0e3d25f943e4ed3d72450cafad38

Tx prefix hash: 796aaf8748f55bfc8d7ccea6fc367aa8f7759a15bba82fd3f2fe1fd3d5205169
Tx public key: 33d5b64a6e3a55d6ae93742d9eb783bfa4a6e9d01905cc13a8bdd5b9c79a8844
Timestamp: 1714578170 Timestamp [UCT]: 2024-05-01 15:42:50 Age [y:d:h:m:s]: 00:254:14:13:03
Block: 1012609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 182224 RingCT/type: yes/0
Extra: 0133d5b64a6e3a55d6ae93742d9eb783bfa4a6e9d01905cc13a8bdd5b9c79a8844

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f97c584d5981fd412518debb014477428249483eae7473ed63ae3e935af18601 0.600000000000 1475189 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": 1012619, "vin": [ { "gen": { "height": 1012609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f97c584d5981fd412518debb014477428249483eae7473ed63ae3e935af18601" } } ], "extra": [ 1, 51, 213, 182, 74, 110, 58, 85, 214, 174, 147, 116, 45, 158, 183, 131, 191, 164, 166, 233, 208, 25, 5, 204, 19, 168, 189, 213, 185, 199, 154, 136, 68 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8