Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f971a28fc1f8d0823303d1e37955c8f8329d4a5d873bc39c0c904d62b3dfabf4

Tx prefix hash: e9c1e12ddf5955e10edbf2cf84e234c13a823a14f5e24fdf3115306985761d6e
Tx public key: f8b30d634162dc34df4570f4ab23071fdbbfe5cd2a9a70ef200de7f74e1a7823
Timestamp: 1709950717 Timestamp [UCT]: 2024-03-09 02:18:37 Age [y:d:h:m:s]: 01:030:14:07:43
Block: 974246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282858 RingCT/type: yes/0
Extra: 01f8b30d634162dc34df4570f4ab23071fdbbfe5cd2a9a70ef200de7f74e1a78230211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5c6aee6797c92997d1a0d2e100f44edac2614c643742ed9c63306620d7dd3a6 0.600000000000 1434201 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": 974256, "vin": [ { "gen": { "height": 974246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5c6aee6797c92997d1a0d2e100f44edac2614c643742ed9c63306620d7dd3a6" } } ], "extra": [ 1, 248, 179, 13, 99, 65, 98, 220, 52, 223, 69, 112, 244, 171, 35, 7, 31, 219, 191, 229, 205, 42, 154, 112, 239, 32, 13, 231, 247, 78, 26, 120, 35, 2, 17, 0, 0, 0, 7, 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