Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7958fdaf84c3392a686cbad7d4de402ddbc0a5c90649e3cbc584308ef6c2c81f

Tx prefix hash: 88613f9eb878a73d9cb3d8738f72918742771070b0fe2309ab7183e348d1bde9
Tx public key: af268fcd0e95a70b2fbd17f1efd1e1dea81989459146b8b49d32fe6d3de9e09f
Timestamp: 1713169226 Timestamp [UCT]: 2024-04-15 08:20:26 Age [y:d:h:m:s]: 00:270:05:04:28
Block: 1000919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193414 RingCT/type: yes/0
Extra: 01af268fcd0e95a70b2fbd17f1efd1e1dea81989459146b8b49d32fe6d3de9e09f02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baf20ef5b8003f12c72d4cdf10e006e3c76ef14803704012a22e0755ea799614 0.600000000000 1461419 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": 1000929, "vin": [ { "gen": { "height": 1000919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baf20ef5b8003f12c72d4cdf10e006e3c76ef14803704012a22e0755ea799614" } } ], "extra": [ 1, 175, 38, 143, 205, 14, 149, 167, 11, 47, 189, 23, 241, 239, 209, 225, 222, 168, 25, 137, 69, 145, 70, 184, 180, 157, 50, 254, 109, 61, 233, 224, 159, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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