Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08ec5fb4d193303982be38c296422b3b8d785cb0b60252462c87a464ca55a219

Tx prefix hash: 9ca1ae9a33c3d2c49590f11d9ce1cf56882a8788ee55e416ec26c878a51192c5
Tx public key: 6577de0301e7156d28b0ba7e0f5f295d87c7907165516f8d424c59df50d19b89
Timestamp: 1705620458 Timestamp [UCT]: 2024-01-18 23:27:38 Age [y:d:h:m:s]: 01:150:22:06:37
Block: 938323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368885 RingCT/type: yes/0
Extra: 016577de0301e7156d28b0ba7e0f5f295d87c7907165516f8d424c59df50d19b8902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35aa1be1ad5677f54c3529ff8acec488838cf6ae2e78552a9198ba33f9c0f8ef 0.600000000000 1396393 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": 938333, "vin": [ { "gen": { "height": 938323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35aa1be1ad5677f54c3529ff8acec488838cf6ae2e78552a9198ba33f9c0f8ef" } } ], "extra": [ 1, 101, 119, 222, 3, 1, 231, 21, 109, 40, 176, 186, 126, 15, 95, 41, 93, 135, 199, 144, 113, 101, 81, 111, 141, 66, 76, 89, 223, 80, 209, 155, 137, 2, 17, 0, 0, 0, 2, 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