Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f09614dd7e4f1e437e84cbf042bdb116d741314b995e580fac878b27fa565bd

Tx prefix hash: 2114c5807457cc188fd8c8394fa8c54fbfae3d52abbbdb74bc2e15e0cb0405bd
Tx public key: c57cc9864a13709a049817acd18d7eced70b7f0b461ce4ccfde4c2a323d54ac4
Timestamp: 1725803942 Timestamp [UCT]: 2024-09-08 13:59:02 Age [y:d:h:m:s]: 00:168:14:29:25
Block: 1105675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120297 RingCT/type: yes/0
Extra: 01c57cc9864a13709a049817acd18d7eced70b7f0b461ce4ccfde4c2a323d54ac4021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e154666a12c68e605e5eb23b9e5cead110bf6a1d524eac95d411cb5802b4f18 0.600000000000 1583094 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": 1105685, "vin": [ { "gen": { "height": 1105675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e154666a12c68e605e5eb23b9e5cead110bf6a1d524eac95d411cb5802b4f18" } } ], "extra": [ 1, 197, 124, 201, 134, 74, 19, 112, 154, 4, 152, 23, 172, 209, 141, 126, 206, 215, 11, 127, 11, 70, 28, 228, 204, 253, 228, 194, 163, 35, 213, 74, 196, 2, 17, 0, 0, 0, 4, 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