Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3821c1a75fdd0458be23c5a61167a2e2f49a1380cade3171c2e95567aa6b76ef

Tx prefix hash: f9b85aa6c41b567141cc2c8b3bb4ddfb192a97dc8292513bd965de59ffb743a1
Tx public key: 8bccb99fde6f7fc2d98aef4f484b2c971160606e14414011db53d19e07aa73b5
Timestamp: 1713700642 Timestamp [UCT]: 2024-04-21 11:57:22 Age [y:d:h:m:s]: 00:307:06:45:00
Block: 1005329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219633 RingCT/type: yes/0
Extra: 018bccb99fde6f7fc2d98aef4f484b2c971160606e14414011db53d19e07aa73b50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a70e7f1b801a3461dedb34b9cf277a06564549d1f1d4672936e84e18d6df9d4 0.600000000000 1465925 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": 1005339, "vin": [ { "gen": { "height": 1005329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a70e7f1b801a3461dedb34b9cf277a06564549d1f1d4672936e84e18d6df9d4" } } ], "extra": [ 1, 139, 204, 185, 159, 222, 111, 127, 194, 217, 138, 239, 79, 72, 75, 44, 151, 17, 96, 96, 110, 20, 65, 64, 17, 219, 83, 209, 158, 7, 170, 115, 181, 2, 17, 0, 0, 0, 2, 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