Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8e7739ae9733a5f3dab9dd6b2c3f76609070d2f83e10048f1ce2724f924bd6f

Tx prefix hash: fd5b4aa73b9c6b4e216107136da608b089ae3bc54d076ac520c8ce866a60df57
Tx public key: 20bbd4ed6bf4f0ca8f71fbcbd89bd8b84108ed4935a802c25ccd195fb51abd89
Timestamp: 1702080332 Timestamp [UCT]: 2023-12-09 00:05:32 Age [y:d:h:m:s]: 01:124:18:54:09
Block: 908994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350335 RingCT/type: yes/0
Extra: 0120bbd4ed6bf4f0ca8f71fbcbd89bd8b84108ed4935a802c25ccd195fb51abd8902110000001533af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 649fe99efac09a2ae107f09c58be211db8cd6948d669e0c62adf50351810a589 0.600000000000 1366059 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": 909004, "vin": [ { "gen": { "height": 908994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "649fe99efac09a2ae107f09c58be211db8cd6948d669e0c62adf50351810a589" } } ], "extra": [ 1, 32, 187, 212, 237, 107, 244, 240, 202, 143, 113, 251, 203, 216, 155, 216, 184, 65, 8, 237, 73, 53, 168, 2, 194, 92, 205, 25, 95, 181, 26, 189, 137, 2, 17, 0, 0, 0, 21, 51, 175, 153, 244, 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