Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4a1aed6c4124676ad978a404ea96aac03651fe2529298dd945f6019ccc1d889

Tx prefix hash: 186d346e70c7dc7619d0cddabe6186e020933f8c1e8cf77f7686c4aa69083fdc
Tx public key: 0620d35b31172d78063eb5d22720f3d15cc3654e942ea1b6f7fa5991e36635e6
Timestamp: 1685907500 Timestamp [UCT]: 2023-06-04 19:38:20 Age [y:d:h:m:s]: 02:158:23:16:07
Block: 775158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 633397 RingCT/type: yes/0
Extra: 010620d35b31172d78063eb5d22720f3d15cc3654e942ea1b6f7fa5991e36635e6021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.657982449000 dcy

stealth address amount amount idx
00: 3552a60dd6f2e011b4ec0b7384abf07677baf5be28f5238f6a7845b985561b17 1.657982449000 1224659 of 0

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": 775168, "vin": [ { "gen": { "height": 775158 } } ], "vout": [ { "amount": 1657982449, "target": { "key": "3552a60dd6f2e011b4ec0b7384abf07677baf5be28f5238f6a7845b985561b17" } } ], "extra": [ 1, 6, 32, 211, 91, 49, 23, 45, 120, 6, 62, 181, 210, 39, 32, 243, 209, 92, 195, 101, 78, 148, 46, 161, 182, 247, 250, 89, 145, 227, 102, 53, 230, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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