Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eb0e2422a112cd0bcf64bacc7fc494e921a4cd9f1fda9885392b91c1d59d59e

Tx prefix hash: 49ae9a5fe0756dcfcac30fc0746c8987ab59aba570370e6d3d134db4727fcd03
Tx public key: 5f1b8cedcc3dcc98f6935db9fe5355fff3d9c0d777c6d64881dbc3535d2d4f38
Timestamp: 1707900708 Timestamp [UCT]: 2024-02-14 08:51:48 Age [y:d:h:m:s]: 01:041:04:35:07
Block: 957235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290474 RingCT/type: yes/0
Extra: 015f1b8cedcc3dcc98f6935db9fe5355fff3d9c0d777c6d64881dbc3535d2d4f380211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fc4eff8a2930fa9f62ce1c5d355b697b5ac010ca85e846f68fe3870347628e3 0.600000000000 1416551 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": 957245, "vin": [ { "gen": { "height": 957235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fc4eff8a2930fa9f62ce1c5d355b697b5ac010ca85e846f68fe3870347628e3" } } ], "extra": [ 1, 95, 27, 140, 237, 204, 61, 204, 152, 246, 147, 93, 185, 254, 83, 85, 255, 243, 217, 192, 215, 119, 198, 214, 72, 129, 219, 195, 83, 93, 45, 79, 56, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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